> Thread 5 return signal frame corrupted. Killing process. Upon return from a signal handler, then valgrind checks the information which the Linux kernel will use to restore the pre-signal state of the thread. valgrind detected that the information was corrupt. The signal handler (or some other thread, or perhaps valgrind) overwrote critical information in the pre-signal state structure (such as the stack pointer, instruction pointer, etc.) and it would be insane for the thread to even attempt to continue executing. The bugs are bad enough that they have totally destroyed the thread.
If there is no possibility that thread 5 was executing a signal handler, then valgrind has lost its mind. Please try to reproduce the problem, then file a bug report; see http://valgrind.org/support/bug_reports.html . -- ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
