|
From: <Joh...@3c...> - 2004-02-04 06:06:55
|
Hi. I am new to valgrind and am running 2.1, which I built from sources for Redhat 9. I get these error reports from valgrind, which surprisingly references the valgrind source itself: ==27188== Conditional jump or move depends on uninitialised value(s) ==27188== at 0x4067A49B: thread_wrapper (vg_libpthread.c:641) ==27188== by 0x40153E87: do__quit (vg_scheduler.c:1787) ==27188== ==27188== Thread 2: ==27188== Conditional jump or move depends on uninitialised value(s) ==27188== at 0x4067A4AF: thread_wrapper (vg_libpthread.c:644) ==27188== by 0x40153E87: do__quit (vg_scheduler.c:1787) ==27188== ==27188== Thread 4: ==27188== thread_wrapper: invalid attr->__detachstate ==27188== at 0x40679C89: pthread_error (vg_libpthread.c:280) ==27188== by 0x4067A4A8: thread_wrapper (vg_libpthread.c:643) ==27188== by 0x40153E87: do__quit (vg_scheduler.c:1787) ==27188== I've had a casual look through the archives and don't see other reports of a similar problem. Please advise. Thanks, John |
|
From: Jeremy F. <je...@go...> - 2004-02-04 17:59:01
|
On Tue, 2004-02-03 at 08:11, Joh...@3c... wrote: > I am new to valgrind and am running 2.1, which I built from sources for > Redhat 9. I get these error reports from valgrind, which surprisingly > references the valgrind source itself: > > ==27188== Conditional jump or move depends on uninitialised value(s) > ==27188== at 0x4067A49B: thread_wrapper (vg_libpthread.c:641) > ==27188== by 0x40153E87: do__quit (vg_scheduler.c:1787) > ==27188== > ==27188== Thread 2: > ==27188== Conditional jump or move depends on uninitialised value(s) > ==27188== at 0x4067A4AF: thread_wrapper (vg_libpthread.c:644) > ==27188== by 0x40153E87: do__quit (vg_scheduler.c:1787) > ==27188== > ==27188== Thread 4: > ==27188== thread_wrapper: invalid attr->__detachstate > ==27188== at 0x40679C89: pthread_error (vg_libpthread.c:280) > ==27188== by 0x4067A4A8: thread_wrapper (vg_libpthread.c:643) > ==27188== by 0x40153E87: do__quit (vg_scheduler.c:1787) > ==27188== > > I've had a casual look through the archives and don't see other reports of > a similar problem. Please advise. That looks like it might be related to the libc_freeres stuff. Do these happen when your program exits, or during its run? J |