Hi everybody,
I've had good luck working with valgrind, but with my recent update of the
valgrind sources this morning from the kde repository my app doesn't
work any longer.
I tried reducing the app down, but it seems that a single source file with
an
empty main gives me the "Assertion 'sane' failed" message when the app
exits.
I tried different snapshots of the valgrind tree and found that version
'2003-10-13 00:00' still works fine, but '2003-10-14 00:00' is broken. I
tried
looking at the diffs, but there was a lot of work done that day. So it's
hard for me to find what exactly is causing this. Hopefully this is enough
information.
Thank you for a great and very helpful tool.
bob
-------
Linux installation:
SuSE 8.2
gcc version 3.3 20030226 (prerelease) (SuSE Linux)
Valgrind:
suppresions: glibc-2.3.supp xfree-4.supp xfree-3.supp
version: HEAD from this morning
command: valgrind -v --run-libc-freeres=no ./vgtest
C++ program:
int main()
{
return 0;
}
Compiled as:
g++ -o vgtest vgtest.cpp -lstdc++
Valgrind output:
==32341== Memcheck, a memory error detector for x86-linux.
==32341== Copyright (C) 2002-2003, and GNU GPL'd, by Julian Seward.
==32341== Using valgrind-HEAD, a program supervision framework for
x86-linux.
==32341== Copyright (C) 2000-2003, and GNU GPL'd, by Julian Seward.
==32341== Command line
==32341== ./vgtest
==32341== Startup, with flags:
==32341== --trace-children=yes
==32341== --num-callers=16
==32341== --suppressions=/opt/valgrind-cvs//lib/valgrind/default.supp
==32341== -v
==32341== --run-libc-freeres=no
==32341== Reading syms from /home/bob/projects/ValgrindTest/vgtest
==32341== Reading syms from /lib/ld-2.3.2.so
==32341== object doesn't have any debug info
==32341== Reading syms from
/opt/valgrind-cvs/lib/valgrind/vgskin_memcheck.so
==32341== Reading syms from /opt/valgrind-cvs/lib/valgrind/valgrind.so
==32341== Reading syms from /usr/lib/libstdc++.so.5.0.3
==32341== object doesn't have any debug info
==32341== Reading syms from /lib/libm.so.6
==32341== object doesn't have any debug info
==32341== Reading syms from /lib/libgcc_s.so.1
==32341== section beyond image end?!
==32341== Reading syms from /lib/libc.so.6
==32341== object doesn't have any debug info
==32341== Reading suppressions file:
/opt/valgrind-cvs//lib/valgrind/default.supp
==32341== Estimated CPU clock rate is 1501 MHz
==32341==
==32341==
==32341== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==32341== malloc/free: in use at exit: 0 bytes in 0 blocks.
==32341== malloc/free: 0 allocs, 0 frees, 0 bytes allocated.
==32341==
--32341-- TID 1: proxy LWP 0 exited with status 0
valgrind: vg_proxylwp.c:1360 (vgPlain_proxy_sanity): Assertion `sane'
failed.
==32341== at 0x40175DF5: vgPlain_skin_assert_fail (vg_mylibc.c:1102)
==32341== by 0x40175DF4: assert_fail (vg_mylibc.c:1098)
==32341== by 0x40175E83: vgPlain_core_assert_fail (vg_mylibc.c:1109)
==32341== by 0x4017A6BA: vgPlain_proxy_sanity (vg_proxylwp.c:1360)
==32341== by 0x40170DDD: vgPlain_do_sanity_checks (vg_main.c:2054)
==32341== by 0x401705F9: vgPlain_main (vg_main.c:1702)
sched status:
Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0
==32341== at 0x403D4AB3: __GI__exit (in /lib/libc.so.6)
==32341== by 0x4033A85E: __libc_start_main (in /lib/libc.so.6)
==32341== by 0x80482C0: (within /home/bob/projects/ValgrindTest/vgtest)
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: valgrind.kde.org
In the bug report, send all the above text, the valgrind
version, and what Linux distro you are using. Thanks.
|