Elephant + Berkley DB

[Daniel Brooks]

Has anyone else used Weblocks with Elephant's Berkely DB storage? All I
get is memory corruption. It happens with 4.6 as well.

Loading /usr/local/BerkeleyDB.4.5/lib/libdb-4.5.so
Attempting to load libberkeley-db.so...
Loaded /home/db48x/src/clbuild/source/elephant/src/db-bdb/libberkeley-db.so
STYLE-WARNING: Implicitly creating new generic function START-DEADLOCK-DETECTOR.
STYLE-WARNING: Implicitly creating new generic function STOP-DEADLOCK-DETECTOR.
STYLE-WARNING: Implicitly creating new generic function CHECKPOINT.
STYLE-WARNING: Implicitly creating new generic function BUILD-BTREE-INDEX.
STYLE-WARNING: Implicitly creating new generic function POPULATE.
CORRUPTION WARNING in SBCL pid 6082(tid 140737353967344):
Memory fault at 4020002 (pc=0x7ffff0053f36, sp=0x7ffff0cb65b0)
The integrity of this image is possibly compromised.
Continuing with fingers crossed.

debugger invoked on a SB-SYS:MEMORY-FAULT-ERROR in thread #<THREAD "initial thread" RUNNING {10029FB8A1}>:
Unhandled memory fault at #x4020002.

Maybe I'll use the clsql+sqlite storage option instead.

db48x

[Leslie P. Polzer]

Daniel Brooks wrote:
>
> Has anyone else used Weblocks with Elephant's Berkely DB storage? All I
> get is memory corruption. It happens with 4.6 as well.

There are quite a bunch of people with that setup.

Questions:

* what's your SBCL version?

* what's your Elephant version?

* does the problem occur only in conjunction with Weblocks?
Try running Elephant without it.

Hope that helps.

Leslie

--
http://www.linkedin.com/in/polzer

[Ian Eslick]

You should be running bdb 4.7 with the latest development head.

Ian

On Sep 13, 2009, at 2:59 PM, Daniel Brooks wrote:

>
> Has anyone else used Weblocks with Elephant's Berkely DB storage?
> All I
> get is memory corruption. It happens with 4.6 as well.
>
> Loading /usr/local/BerkeleyDB.4.5/lib/libdb-4.5.so
> Attempting to load libberkeley-db.so...
> Loaded /home/db48x/src/clbuild/source/elephant/src/db-bdb/
> libberkeley-db.so
> STYLE-WARNING: Implicitly creating new generic function START-
> DEADLOCK-DETECTOR.

> STYLE-WARNING: Implicitly creating new generic function STOP-
> DEADLOCK-DETECTOR.

[Daniel Brooks]

Ian Eslick <esl...@media.mit.edu> writes:

> You should be running bdb 4.7 with the latest development head.
>
> Ian

Ah, that works better. It doesn't quite work (error 22 on reading the
database), but that may just be because I need to pull more recent
elephant updates from the repository.

Thanks,

db48x

[Ian Eslick]

An error 22 sounds suspicious. Is this when running the test suite
after deleting the existing DB's?

Ian