Re: [Valgrind-users] valgrind with a bad exit

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

On Tue, 2003-12-30 at 08:25, Diego Torres wrote:
> It's normal that valgrind(2.1.0, debian unstable) exits like these (with this error msg) ?
> 
> ==31011== Invalid read of size 1
> ==31011==    at 0x40385546: __GI__dl_close (dl-close.c:122)
> ==31011==    by 0x403863CA: do_dlclose (dl-libc.c:96)
> ==31011==    by 0x4000BF15: _dl_catch_error (in /lib/ld-2.3.2.so)
> ==31011==    by 0x4038630D: dlerror_run (dl-libc.c:42)
> ==31011==  Address 0x1E7 is not stack'd, malloc'd or free'd
> ==31011==
> ==31011== Process terminating with default action of signal 11 (SIGSEGV): dumping core
> ==31011==  Address not mapped to object at address 0x1E7
> ==31011==    at 0x40385546: __GI__dl_close (dl-close.c:122)
> ==31011==    by 0x403863CA: do_dlclose (dl-libc.c:96)
> ==31011==    by 0x4000BF15: _dl_catch_error (in /lib/ld-2.3.2.so)
> ==31011==    by 0x4038630D: dlerror_run (dl-libc.c:42)
> ==31011==
> ==31011== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 2 from 1)
> ==31011== malloc/free: in use at exit: 1876 bytes in 9 blocks.
> ==31011== malloc/free: 44 allocs, 35 frees, 4119 bytes allocated.
> ==31011== For a detailed leak analysis,  rerun with: --leak-check=yes
> ==31011== For counts of detected errors, rerun with: -v
> Segmentation fault

Hm, this works for me here, so I think it's version-specific.  Could you
run it again, with --num-callers=10?  Also, what's the full version of
glibc?

	J