My apologies, it appears I have found the cause of the problem. Since the software when run by itself generated core dumps just fine I assumed core ulimit was set to something other than 0. Turns out my assumption was incorrect. After changing it to unlimited, valgrind acts as desired.
Again, my apologies for the inconvenience. Pol Julian Seward wrote: >> Normally, SIGABRT triggers a core dump according to the man pages. So >> why doesn't valgrind dump the core? > > Um, I don't know. What architecture are you running on? Can you send a > small test case program that shows the problem? > > J ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
