|
From: Nicholas N. <nj...@cs...> - 2005-09-12 21:03:31
|
On Mon, 12 Sep 2005, Fielder, Todd Patrick wrote: >> I'm new to valgrind, and am attempting to use cachegrind, but am >> receiving the following error: Any ideas? >> >> ==10326== >> ==10326== Stack overflow in thread 0: can't grow stack to 0x0 >> --10326-- INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting >> --10326-- si_code=1 Fault EIP: 0xB002F580; Faulting address: 0x0 >> --10326-- esp=0xB04F6CFC >> >> >> valgrind: the `impossible' happened: >> Killed by fatal signal >> Basic block ctr is approximately 402065958 >> ==10326== at 0xB002F580: vgPlain_strlen (vg_mylibc.c:718) >> ==10326== by 0xB101A781: fprint_CC_table_and_calc_totals (cg_main.c:833) >> ==10326== by 0xB101AA52: vgSkin_fini (cg_main.c:914) >> ==10326== by 0xB005BCD7: vgSkinInternal_fini (vg_toolint.c:36) >> ==10326== by 0xB002A928: vgPlain_shutdown_actions (vg_main.c:2689) >> ==10326== by 0xB0070809: vgArch_thread_wrapper (core_os.c:77) > > Thanks for responding, the output of memcheck is: > [snip] > and the output of --tool=none is: > [snip] So it's Cachegrind-specific... it's a very strange stack trace, it says the problem is in VG_(strlen)(), which is a very simple function and seems unlikely to cause such a crash. A workaround would be to try just commenting out the line in question -- you won't get a "cmd:" line in your cachegrind.out file but that doesn't matter very much. As for fixing the bug -- can you provide a small test case? Without one it will be hard to know what's going on. Nick |