Version: 3.4.0 (using KDE 4.2.1) OS: Linux Installed from: Fedora RPMs Valgrind reports a program exiting from a signal such as SEGV, FPE, etc. along with a cause. It would be nice if XML output reported these errors also.
Add exec() to the list of app-terminating events it'd be nice to handle more nicely in xml. One of Timur's fork() patches does that.
The patch Dan is talking about is attached here https://bugs.kde.org/show_bug.cgi?id=162848
*** Bug 200544 has been marked as a duplicate of this bug. ***
Created attachment 92237 [details] Print fatal signal also in xml This patch prints fatal (terminating) signals also in xml output.
Created attachment 92548 [details] Print fatal signals more often (v2) Print fatal signal info also in xml output The callstack is printed for: * xml output * verbose output * if signal is from kernel and the signal can trigger a coredump * if signal is from the thread itself (calling raise) This will support debugging by making calls to abort visible in valgrind output.
Created attachment 92598 [details] Print fatal signals more often (v3) Check that is_signal_from_kernel thinks it is not from kernel. Then compare si_pid against the pid values of all threads. This one also catches tgkill calls from other threads. Extend test gone.c to have arguments abortchild and abortparent. TODO: Document the resulting xml.
Created attachment 92666 [details] print fatal signal in xml Add updated patch (based on trunk rev. 15252) that only adds printing the signal callstack to xml.
Created attachment 94456 [details] Print fatal signal in xml - V2 The core is changed to write the callstack to xml when a fatal signal happens. It adds a testcase and also documents the extended xml format.
can this be commited?
Committed (slightly modified) in revision 15747 Thanks for the patch, sorry for the long time taken to look and commit it.