|
From: Eyal L. <ey...@ey...> - 2005-02-21 22:26:57
|
Jeremy Fitzhardinge wrote: > Eyal Lebedinsky wrote: [trimmed report of program crashing] > Well, --quiet will suppress the printing about SIGSEGVs, so you wouldn't > see any crash messages. If it crashes after exit(), it could still be > some atexit/static destructor calls which are causing the problem. My programs are pure C and use no atexit(). > Does it generate a vgcore file? No. > Well, the changes to memcheck reduced its memory use by a large amount > in a lot of common cases I was hoping for just this. > so it could be that you're just getting further? No. In the past I could run a few hundred tests before the server crashes. Now a smaller program (a client) crashes every time it runs. It has a very much smaller memory footprint than the server. > Yes, please: strace, -v, --trace-syscalls=yes and --trace-signals=yes . Sure. I am afraid the log is biggish, but it compresses well. It seems to me that it should have had something after the last line logged: ==2005-02-22 09:03:53.660 15910== ==2005-02-22 09:03:53.660 15910== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 43 from 1) --2005-02-22 09:03:53.660 15910-- --2005-02-22 09:03:53.660 15910-- supp: 43 Ugly strchr error in /lib/ld-2.3.2.so ==2005-02-22 09:03:53.660 15910== malloc/free: in use at exit: 4765 bytes in 50 blocks. ==2005-02-22 09:03:53.660 15910== malloc/free: 10735 allocs, 10685 frees, 99923376 bytes allocated. ==2005-02-22 09:03:53.660 15910== ==2005-02-22 09:03:53.660 15910== searching for pointers to 50 not-freed blocks. > And file a bug in bugzilla. http://bugs.kde.org/show_bug.cgi?id=99949 -- Eyal Lebedinsky (ey...@ey...) <http://samba.org/eyal/> attach .zip as .dat |