Re: [elephant-devel] elephant64

2006-10-02 Thread Marco Baringer
Ian Eslick <[EMAIL PROTECTED]> writes: > I've sometimes noticed that there is an odd blockage and that running > "db_deadlock -a o -t 0.1" on the database resolves it. It's possible > it's a locking problem caused by the way that transactions are allocated > in the low level lisp code. Try openi

Re: [elephant-devel] elephant64

2006-10-02 Thread Marco Baringer
Ian Eslick <[EMAIL PROTECTED]> writes: > #1 - I haven't seen the fp overflow problem before, however. > > A couple of thoughts. > > The system does read some values from the DB after open. You might > trace the db-bdb/bdb-controller function to see where it's failing - > that might help us have

Re: [elephant-devel] elephant64

2006-10-02 Thread Ian Eslick
FYI - The biggest change in the current CVS is a simple update to use BDB 4.4 instead of 4.3. I don't believe we have yet promoted any API changes yet. Ian Marco Baringer wrote: > i'm currently trying to get elephant to run on sbcl x86-64. i've > patched memutil and sleepycat.lisp heavily to rem

Re: [elephant-devel] elephant64

2006-10-02 Thread Ian Eslick
Can you get us temporary access to your 64-bit machine to do some experimentation? We had another user go through this same problem on an AMD awhile back and it's hard for Robert and I to test because neither of us have a 64-bit machine available. #2 - The double definition is intentional - it's