[elephant-devel] Problem with LWW 5.1.2, BDB-backend

[Plamen .]

Hello Ian, Elliott,

now I (learned some GDB, btw, Elliott - ty a lot for the compiler
options for GCC) debugged also the C side of the Elephant under
LWW-32bit/BDB 4.7.25 and... everything looks ok as ordered by the
Lisp-side of the inteface - all parameters to the db_env_open are
passed as expected (the pathname of the home dir, the flags (1493 =
create t & init-mpool t & thread t & init-lock t & init-log t &
init-txn t & recover t) as well the ENV object...

So - it seems - it's not an even an UFFI problem - either BDB on
Windows expects some additional setup in the ENV which is not yet in
the Lisp code (except the max-transactions and max-locks which I don't
know why also give the error 22 : Invalid argument) or if not in the
ENV struct - using may be some additional API call....

So - I'm going now  to delve in the BDB doc. Hopefully I see something
which we miss.

Greets


On Tue, Dec 8, 2009 at 10:35 PM, Ian Eslick <eslick at media.mit.edu> wrote:
> I don't think BDB 4.7 has been tested on windows until now.  I'm surprised
> 4.5 works with the latest head - but it's probably because you aren't
> exercising some of the 4.7 features Leslie added.
> On Dec 8, 2009, at 1:14 PM, Elliott Slaughter wrote:
>
> On Tue, Dec 8, 2009 at 12:19 PM, Ian Eslick <eslick at media.mit.edu> wrote:
>>
>> Elliott - these DLLs work on your system w/ Lispworks?  Is everything
>> working for you?  I just want to make sure we have a baseline.
>
> I went back to my Windows XP build, which I know worked once upon a time,
> and updated to the newest Elephant. With BDB 4.5 and 4.7 installed
> side-by-side, I configured Elephant to use 4.5: the build worked fine. I
> reconfigured for 4.7, and the build broke with error 22. Back to 4.5: build
> works fine. Back again to 4.7: still broken.
> Has Elephant ever been tested against BDB 4.7 on Windows?
> At any rate, I can supply dlls which I know work for BDB 4.5 (attached).
> They work with the newest version of Elephant.
> By the way, line 65 of ele-bdb.asd is hard coded to "-ldb45". That probably
> needs to change. (But it doesn't solve our bug; I already fixed it local and
> it didn't help.)
> Hope that helps?
> --
> Elliott Slaughter
>
> "Don't worry about what anybody else is going to do. The best way to predict
> the future is to invent it." - Alan Kay
> <elephant-1.0-windows-bdb45.7z>_______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel
>
> _______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel
>