On 17/06/11 13:44, Stephanie Stroka wrote: > running my program with valgrind gives me the following hints: > > > - --15446-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 > (SIGSEGV) - exiting > - --15446-- si_code=1; Faulting address: 0x2D11153860; sp: 0x40317bdd0 > > valgrind: the 'impossible' happened: > Killed by fatal signal > ==15446== at 0x38032A94: unlinkBlock (m_mallocfree.c:245) > ==15446== by 0x3803453D: vgPlain_arena_malloc (m_mallocfree.c:1381) > ==15446== by 0x3800292E: vgMemCheck_new_block (mc_malloc_wrappers.c:201) > ==15446== by 0x38002C98: vgMemCheck_malloc (mc_malloc_wrappers.c:238) > ==15446== by 0x3806140E: vgPlain_scheduler (scheduler.c:1394) > ==15446== by 0x3808598A: run_a_thread_NORETURN (syswrap-linux.c:94)
Well that's not really a hint, that's when everything has gone bad. What you want to look for is messages before that about writing to things you shouldn't be writing to. Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
