Ian, luckily I am in the development stages of my app, so I can freely
throw away my data whenever I like (it is just syslog data from some
very chatty networking hardware, so there is always more to be had). I
have experienced these issues on 32 and 64 bit systems, though my main
system is 6
This is very odd behavior. I have a live webapp that uses all this
stuff pretty heavily.
I did see this active cursor message earlier, but it was due to some
debugging churn in the BDB transaction handler a day or two ago.
Those issues should all be resolved now, but it's possible somethin
Unfortunately, things remain as before. Here is some additional debug
output that I found in the *inferior-lisp* buffer of my emacs session:
Deserialization error in map: returning nil for element
transaction has active cursors
PANIC: Invalid argument
PANIC: DB_RUNRECOVERY: Fatal error, run data
Thanks, Ian. All tests pass for me as well. I am running my
application with the new code and will let you know how it goes.
Thanks again!
Kevin
Ian Eslick wrote:
> I just checked in a few more fixes a few minutes ago. I finally was
> able to reproduce some of this locally. Try cleaning ou
I just checked in a few more fixes a few minutes ago. I finally was
able to reproduce some of this locally. Try cleaning out the test
database and re-running the tests. Everything passes for me on a
fresh DB and my own application is running fine too.
Ian
On Jan 10, 2009, at 2:04 PM, Kev
After pulling the latest patches and rebuilding without optimizations as
you suggest, I get the following errors, the second of which is slightly
different than what I was receiving previously.
First, a deserialization error:
Condition ELEPHANT-TYPE-DESERIALIZATION-ERROR was signalled.
[Cond
