|
From: Kerrick S. <ma...@ke...> - 2012-10-04 18:23:50
|
Hello, The following message appears in Valgrind's output: Thread 5 return signal frame corrupted. Killing process. What exactly does this message mean? It looks like the thread attempted to dereference a NULL pointer immediately before the message was printed, so I'm guessing that the message just serves to inform the user that the thread segfaulted and so the process is now exiting. - Kerrick |
|
From: John R. <jr...@bi...> - 2012-10-04 18:57:48
|
> 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 . -- |