![]() | |
#21
| |||
| |||
|
|
Nope. "make test" should run the version in the blib directory and ignore whatever is installed. Do you have an environment variable, like LD_LIBRARY_PATH that points to the Berkeley DB 3.3 library? |
#22
| |||
| |||
|
|
In article <22fa329d.0308200049.218efd6e (AT) posting (DOT) google.com>, Paul.Marquess (AT) btinternet (DOT) com (Paul Marquess) writes: Sorry, I understand your use of Trace to get debugging info. What I don't get is the part about error codes not being updated. The only thing I can think of is that errno will probably get reset if you use Trace in it's current form. Oh. What I meant by that was that in my original test case that was failing under 3.3, the only way I found out that _db_cursor() was returning error 22 was by enabling TRACE. It would have been nice if error 22 showed up in BerkeleyDB::Error. Otherwise, there was absolutely no indication of the error except that the method was returning an undefined value. It seems that the error code is making it into the BerkeleyDB object: if ((db->Status = db_cursor(db, db->txn, &cursor, flags)) == 0){ So I don't understand why BerkeleyDB::Error did not show the error. |
![]() |
| Thread Tools | |
| Display Modes | |
| |