|
From: Bill S. <bi...@cl...> - 2004-10-14 16:31:37
|
Upon downloading valgrind 2.2.0 sources and compiling (after editing out some ppdev ioctl defines that don't exist on my driver). I get the following when trying to run. In fact version below is 2.3.0.CVS which gives the same error (but I didn't need to edit this version to compile). Can anyone help? valgrind --tool=memcheck ls -l ==31060== Memcheck, a memory error detector for x86-linux. ==31060== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward et al. ==31060== Using valgrind-2.3.0.CVS, a program supervision framework for x86-linux. ==31060== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward et al. ==31060== For more details, rerun with: -v ==31060== ==31060== Conditional jump or move depends on uninitialised value(s) ==31060== at 0x1B8E6011: _dl_start (do-rel.h:46) ==31060== by 0x1B8E5DB5: (within /lib/ld-2.2.2.so) ==31060== ==31060== Conditional jump or move depends on uninitialised value(s) ==31060== at 0x1B8E60B8: _dl_start (do-rel.h:63) ==31060== by 0x1B8E5DB5: (within /lib/ld-2.2.2.so) ==31060== ==31060== Invalid read of size 4 ==31060== at 0x1B8E6318: _dl_start_final (rtld.c:263) ==31060== by 0x1B8E6089: _dl_start (rtld.c:199) ==31060== by 0x1B8E5DB5: (within /lib/ld-2.2.2.so) ==31060== Address 0x52BFDD1C is just below %esp. Possibly a bug in GCC/G++ ==31060== v 2.96 or 3.0.X. To suppress, use: --workaround-gcc296-bugs=yes ==31060== valgrind: vg_libpthread.c:2333 (read): Assertion `read_ptr != ((void *)0) && read_ptr != read' failed. ==31060== Please report this bug at: valgrind.kde.org ==31060== ==31060== ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 2 from 1) ==31060== malloc/free: in use at exit: 598 bytes in 4 blocks. ==31060== malloc/free: 4 allocs, 0 frees, 598 bytes allocated. ==31060== For a detailed leak analysis, rerun with: --leak-check=yes ==31060== For counts of detected errors, rerun with: -v Bill Somerville |
|
From: David E. <tw...@us...> - 2004-10-14 17:01:33
|
On Thu, 2004-10-14 at 18:25, Bill Somerville wrote:
> Upon downloading valgrind 2.2.0 sources and compiling (after editing out
> some ppdev ioctl defines that don't exist on my driver). I get the
> following when trying to run. In fact version below is 2.3.0.CVS which
> gives the same error (but I didn't need to edit this version to
> compile).
>
> [snip]
>
> ==31060== Address 0x52BFDD1C is just below %esp. Possibly a bug in
> GCC/G++
> ==31060== v 2.96 or 3.0.X. To suppress, use:
> --workaround-gcc296-bugs=yes
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Did you try the suggested parameter to valgrind?
Btw, you never wrote anything about your Linux distribution, kernel
version or compiler.
--
Regards,
-\- David Eriksson -/-
SynCE - http://synce.sourceforge.net
CalcEm - http://calcem.sourceforge.net
ScummVM - http://scummvm.sourceforge.net
Desquirr - http://desquirr.sourceforge.net
SetiWrapper - http://setiwrapper.sourceforge.net
|
|
From: Dirk M. <dm...@gm...> - 2004-10-14 17:05:08
|
On Thursday 14 October 2004 18:25, Bill Somerville wrote: > Upon downloading valgrind 2.2.0 sources and compiling (after editing out > some ppdev ioctl defines that don't exist on my driver). I get the > following when trying to run. In fact version below is 2.3.0.CVS which > gives the same error (but I didn't need to edit this version to > compile). which distribution are you using? Dirk |
|
From: Tom H. <th...@cy...> - 2004-10-14 17:15:39
|
In message <416...@cl...>
Bill Somerville <bi...@cl...> wrote:
> valgrind: vg_libpthread.c:2333 (read): Assertion `read_ptr != ((void
> *)0) && read_ptr != read' failed.
Bug 88614 is the current record for this problem.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|
|
From: Bill S. <bi...@cl...> - 2004-10-14 18:03:42
|
Tom Hughes wrote: > > In message <416...@cl...> > Bill Somerville <bi...@cl...> wrote: > > > valgrind: vg_libpthread.c:2333 (read): Assertion `read_ptr != ((void > > *)0) && read_ptr != read' failed. > > Bug 88614 is the current record for this problem. Thanks for that - I hadn't spotted that. Not sure I can add much, I'm using gcc 3.4.2 to build with libc.so.6 libgcc_s.so.1 I'll watch that bug for a fix. Had a look at the code and it appears to be intercepting read() calls in libpthread but why it can't lookup the dyn symbol I've got no idea. Perhaps the dlopen isn't getting called for some reason (or its been dlclosed). By the way I always have trouble looking up bugs in Bugzilla, can you summarize how you found that; my searches invariably find no bugs at all! > > Tom > > -- > Tom Hughes (th...@cy...) > Software Engineer, Cyberscience Corporation > http://www.cyberscience.com/ > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give us > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users Bill Somerville |