On Wed, Apr 15, 2009 at 6:31 AM, Graham Mark <[email protected]> wrote: > > I'm trying to track down the cause of a seg fault in my MPI program. > Here's what happens with valgrind. > > % mpirun -n 27 ../../valgrind-3.4.1/bin/valgrind --kernel- > variant=bproc mc3_op > ERROR: ld.so: object '/usr/projects/dark/gam/valgrind/amd64-linux/ > libmpiwrap.so' from LD_PRELOAD cannot be preloaded: ignored. > [many other errors reported: conditional jump or move...; > uninitialized data; all trace to library routines] > [program nearly completes and then:] > > --30441-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 > (SIGSEGV) - exiting > --30441-- si_code=80; Faulting address: 0x0; sp: 0x403087d60 > > valgrind: the 'impossible' happened: > Killed by fatal signal > ==30441== at 0x380323E0: vgPlain_arena_free (m_mallocfree.c:218) > ==30441== by 0x38001B17: die_and_free_mem (mc_malloc_wrappers.c:123) > ==30441== by 0x3804AEB4: vgPlain_scheduler (scheduler.c:1303) > ==30441== by 0x3804D44E: run_a_thread_NORETURN (syswrap-linux.c:89)
It's almost certainly caused by heap corruption due to the errors Valgrind reports about your program. If you fix those, this crash will almost certainly go away. Nick ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
