[Valgrind-developers] Always write callstack of signal that kills process

[Matthias S. <zz...@ge...>]

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).

when running valgrind with option "-v" it prints this:

==10481== Process terminating with default action of signal 6 (SIGABRT)
==10481==    at 0x5085137: kill (syscall-template.S:81)
==10481==    by 0x40081B: main (gone.c:26)

But "-v" is too verbose for normal runs :)

So I suggest to always write this and additionally to also do it for xml
output.

I did some experiments. What do you think about something like this in
the xml file:

<fatal_signal>
  <tid>1</tid>
  <signo>6</signo>
  <signame>SIGABRT</signame>
  <stack>
    <frame>
      <ip>0x5084137</ip>
      <obj>/lib64/libc-2.20.so</obj>
      <fn>kill</fn>

<dir>/var/tmp/portage/sys-libs/glibc-2.20-r2/work/glibc-2.20/signal/../sysdeps/unix</dir>
      <file>syscall-template.S</file>
      <line>81</line>
    </frame>
    <frame>
      <ip>0x40081B</ip>
      <obj>/home/matze/development/valgrind.git/gdbserver_tests/gone</obj>
      <fn>main</fn>
      <dir>/home/matze/development/valgrind.git/gdbserver_tests</dir>
      <file>gone.c</file>
      <line>26</line>
    </frame>
  </stack>
</fatal_signal>

Regards
Matthias