|
From: Duncan S. <bal...@fr...> - 2007-11-12 17:00:33
|
I built valgrind from svn of a few hours ago, and ran memcheck (valgrind --tool=memcheck --db-attach=yes) on a multithreaded program. At startup I get: ==11934== Memcheck, a memory error detector. ==11934== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al. ==11934== Using LibVEX rev 1672M, a library for dynamic binary translation. ==11934== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP. ==11934== Using valgrind-3.3.0.SVN, a dynamic binary instrumentation framework. ==11934== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al. ==11934== For more details, rerun with: -v ==11934== ------ IMark(0x4000810, 2) ------ Memcheck: the 'impossible' happened: hasBogusLiterals ==11934== at 0x38017CFB: report_and_quit (m_libcassert.c:140) ==11934== by 0x38017E1D: panic (m_libcassert.c:210) ==11934== by 0x38017E55: vgPlain_tool_panic (m_libcassert.c:225) ==11934== by 0x38012B35: vgMemCheck_instrument (mc_translate.c:3298) ==11934== by 0x38089EFB: LibVEX_Translate (vex_main.c:500) ==11934== by 0x3802B3D2: vgPlain_translate (m_translate.c:1417) ==11934== by 0x38034CB3: vgPlain_scheduler (scheduler.c:762) ==11934== by 0x3804AA35: run_a_thread_NORETURN (syswrap-linux.c:87) sched status: running_tid=1 Thread 1: status = VgTs_Runnable ==11934== at 0x4000810: (within /lib/ld-2.6.1.so) Any idea what could be causing this and what to do about it? Thanks, Duncan. PS: I updated in order to play with helgrind (which doesn't seem to have this problem). Thanks for bringing helgrind back to life! |
|
From: Julian S. <js...@ac...> - 2007-11-12 20:49:18
|
> Any idea what could be causing this and what to do about it? The recent Helgrind merge changed a bunch of internal interfaces. I'm pretty sure this will go away if you rebuild from clean: make distclean (not merely clean) and start over. > PS: I updated in order to play with helgrind (which doesn't seem to > have this problem). Thanks for bringing helgrind back to life! :-) J |
|
From: Duncan S. <bal...@fr...> - 2007-11-13 09:03:30
|
On Monday 12 November 2007 21:48:32 Julian Seward wrote: > > > Any idea what could be causing this and what to do about it? > > The recent Helgrind merge changed a bunch of internal interfaces. > I'm pretty sure this will go away if you rebuild from clean: > make distclean (not merely clean) and start over. You were right: doing "distclean" fixed it - thanks! And thanks again for this fine tool. Best wishes, Duncan. |
|
From: Aleix <ale...@gm...> - 2007-11-13 11:02:32
|
Fixed this issue for me too! :) On Nov 12, 2007 9:48 PM, Julian Seward <js...@ac...> wrote: > > > Any idea what could be causing this and what to do about it? > > The recent Helgrind merge changed a bunch of internal interfaces. > I'm pretty sure this will go away if you rebuild from clean: > make distclean (not merely clean) and start over. > > > PS: I updated in order to play with helgrind (which doesn't seem to > > have this problem). Thanks for bringing helgrind back to life! > > :-) > > J > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > |