|
From: Julian S. <js...@ac...> - 2005-09-12 21:24:51
|
> >> ==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) > > 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. Is it possible that fprint_CC_table_and_calc_totals could have passed NULL to vgPlain_strlen? J |