|
From: Tom H. <to...@co...> - 2005-02-10 14:44:01
|
In message <Pin...@jd...>
Igmar Palsenberg <mai...@jd...> wrote:
>> 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.
>
> The error is probably due to the kernel lacking support for futexes.
> Usually an export LD_ASSUME_KERNEL=2.4.0 fixes this. Valgrind should
> support native pthreads in the CVS version, no idea if it supports
> futexes.
It supports futexes just fine. So does 2.2.0 in fact, it's just that
our libpthread didn't use them so unless you used then directly you
would never see them.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|