|
From: Donald Z. <don...@am...> - 2005-08-16 21:32:52
|
I am trying to use valgrind on Redhat Enterprise Linux 3, Update 5 on x86_64 and am getting the following error. Can anyone tell me what this means and if there is a way to fix it? ==12634== Memcheck, a memory error detector. ==12634== Copyright (C) 2002-2005, and GNU GPL'd, by Julian Seward et al. ==12634== Using LibVEX rev 1313, a library for dynamic binary translation. ==12634== Copyright (C) 2004-2005, and GNU GPL'd, by OpenWorks LLP. ==12634== Using valgrind-3.0.0, a dynamic binary instrumentation framework. ==12634== Copyright (C) 2000-2005, and GNU GPL'd, by Julian Seward et al. valgrind: symtab.c:377 (vgModuleLocal_addCfiSI): Assertion 'cfisi->len > 0 && cfisi->len < 2000000' failed. ==12634== at 0x7001A7BD: ??? sched status: running_tid=0 Note: see also the FAQ.txt in the source distribution. It contains workarounds to several common problems. If that doesn't help, please report this bug to: www.valgrind.org In the bug report, send all the above text, the valgrind version, and what Linux distro you are using. Thanks. Thanks -- Donald Zoch don...@am... |
|
From: Nicholas N. <nj...@cs...> - 2005-08-28 05:01:57
|
On Tue, 16 Aug 2005, Donald Zoch wrote: > I am trying to use valgrind on Redhat Enterprise Linux 3, Update 5 > on x86_64 and am getting the following error. Can anyone tell me what > this means and if there is a way to fix it? > > ==12634== Memcheck, a memory error detector. > ==12634== Copyright (C) 2002-2005, and GNU GPL'd, by Julian Seward et al. > ==12634== Using LibVEX rev 1313, a library for dynamic binary translation. > ==12634== Copyright (C) 2004-2005, and GNU GPL'd, by OpenWorks LLP. > ==12634== Using valgrind-3.0.0, a dynamic binary instrumentation framework. > ==12634== Copyright (C) 2000-2005, and GNU GPL'd, by Julian Seward et al. > > valgrind: symtab.c:377 (vgModuleLocal_addCfiSI): Assertion 'cfisi->len > 0 && cfisi->len < 2000000' failed. > ==12634== at 0x7001A7BD: ??? Just disabling the assertion might work. Not very nice, but if it gets you going again... If you can give a small test case that exhibits this behaviour that would be very helpful. It will have to be an executable, since this is a problem if debug info reading. Nick |