Well, based on the stat output it appears that you don't have any
resource issues so something else must be going on.
Can you break this down to a test case? Also, have you tried running
this with elephant-unstable?
Thanks,
Ian
On Oct 2, 2008, at 2:57 AM, Red Daly wrote:
Unfortunately I am still getting allocation errors even after
increasing the cache size to 1.2 gigabytes and eliminating all
transactions from my application. I have included db_stat output--
the only alarming aspect is the section about mutexes. Do I need
more memory dedicated to storing mutexes? 90 megabytes seems
sufficient to me. (see attachment)
here's some output from the lisp side:
*** glibc detected *** /usr/local/bin/sbcl: malloc(): memory
corruption: 0x000000000065c910 ***
======= Backtrace: =========
/lib/libc.so.6[0x7f5dfa799a14]
/lib/libc.so.6(__libc_malloc+0x90)[0x7f5dfa79b360]
/usr/local/BerkeleyDB.4.5/lib/libdb-4.5.so(__os_malloc+0x6c)
[0x7f5df704bf2c]
/usr/local/BerkeleyDB.4.5/lib/libdb-4.5.so(__os_calloc+0x2a)
[0x7f5df704c06a]
/usr/local/BerkeleyDB.4.5/lib/libdb-4.5.so(db_env_create+0x2d)
[0x7f5df701cb7d]
/home/red/lib/cl/site/elephant/src/db-bdb/libberkeley-db.so(db_env_cr
+0x16)[0x7f5df6d692c6]
[0x100491019b]
Any idea what's going wrong here? I'd like to debug it a little
more (maybe see an additional error log from bdb), but I can't quite
figure out what to do. Right now all I'm getting is the error code
and its message from elephant.
This is with elephant 0.9.1 and bdb 4.5.20. Would a patch of
elephant to support the 4.7 bdb be in order?
Thanks,
Red Daly
<db-stat-results>_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
