|
From: t. s. u. <sc...@ap...> - 2005-02-10 06:09:13
|
On Wed, 2005-02-09 at 14:17 -0500, Jeff Woods (Boca Raton ) wrote: > I am having trouble getting valgrind to work with an application which > uses the Berkeley DB library. The error I am getting is: > > [8305] ERROR: db_env->open: Function not implemented (main.c:1788) > [8305] ERROR: Abnormal exit status (from main.c:1789): 1 > ==8305== > ==8305== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 59 from 1) > ==8305== malloc/free: in use at exit: 264271 bytes in 651 blocks. > ==8305== malloc/free: 722 allocs, 71 frees, 267037 bytes allocated. > ==8305== For a detailed leak analysis, rerun with: --leak-check=yes > ==8305== For counts of detected errors, rerun with: -v > > Note that the lines prefixed by the PID in brackets are generated by my > application. The error is not within valgrind itself (it is being > returned from a dbenv->open() call in the Berkeley DB library), but > valgrind does seem to be triggering this error. The application will > run normally outside of valgrind, but fails consistently at this point > when run under valgrind. I will trim down my application to a bare > minimum of code to reprodcuce this problem and post it here if necessary. I've seen the same thing, environment open hangs in valgrind, but not with all version of linux we test on. I found this post: http://groups-beta.google.com/group/comp.databases.berkeley- db/browse_thread/thread/af5930696f77ff9e/9f8cea87300debd8? q=valgrind&_done=%2Fgroup%2Fcomp.databases.berkeley-db%2Fsearch%3Fgroup% 3Dcomp.databases.berkeley-db%26q%3Dvalgrind%26qt_g%3D1%26searchnow% 3DSearch+this+group%26&_doneTitle=Back+to+Search&&d#9f8cea87300debd8 which suggested rebuilding berkeley '--with-mutex=x86/gcc-assembly'. This worked for me, though I'm less than satisfied with this work around: I'd rather test with the production builds of the libraries. -- t. scott urban <sc...@ap...> |