|
From: Matthias S. <zz...@ge...> - 2015-05-02 11:43:52
|
On 26.04.2015 21:12, Matthias Schwarzott wrote: > On 12.04.2015 20:53, Matthias Schwarzott wrote: >> Hi there! >> >> When executing valgrind automatically on a server, I sometimes wonder if >> a process did finish successfully or did call abort (or was killed in >> some other way). >> > > I modified valgrind to always print the info about a terminating signal > to the xml output. > > Patch is attached here: > https://bugs.kde.org/show_bug.cgi?id=191069 > > About always printing the signal to normal stderr: Maybe there should be > a cmdline option to enable this. > Hi, I suggest this behaviour: For xml and text output should always report callstack of fatal signal. Maybe xml output could also contain the exitcode in case of a normal exit. Currently a callstack is shown if the signal is from kernel and only for text output. But I think a SIGABRT should be reported always, but it does not count as kernel-generated. It might be caused by a call to abort or assert(false) and that is interesting for me. Regards Matthias |