|
From: Ashley P. <as...@qu...> - 2007-02-21 13:14:21
|
As discussed on valgrind-users here is a patch to add the offset into a
seginfo to each frame of a stack trace when using xml. This allows you
to use external tools to resolve symbols if required.
Ashley,
<error>
<tid>1</tid>
<kind>Signal</kind>
<signal>11</signal>
<what>Process terminating with default action of signal 11 (SIGSEGV):
dumping core</what>
<event>Access not within mapped region</event>
<address>0x2</address>
<stack>
<frame>
<ip>0x4907121</ip>
<obj>/opt/valgrind-3.3.0.SVN-quadrics-20070215/lib/valgrind/amd64-linux/vgpreload_memcheck.so</obj>
<offset>0x4121</offset>
<fn>memcpy</fn>
<dir>/home/ashley/q/valgrind/working/valgrind/memcheck</dir>
<file>mc_replace_strmem.c</file>
<line>402</line>
</frame>
<frame>
<ip>0x4004BF</ip>
<obj>/tmp/a.out</obj>
<offset>0x4004BF</offset>
<fn>main</fn>
<dir>/tmp</dir>
<file>segv.c</file>
<line>3</line>
</frame>
</stack>
</error>
$ addr2line
--exe /opt/valgrind-3.3.0.SVN-quadrics-20070215/lib/valgrind/amd64-linux/vgpreload_memcheck.so 0x4121
/home/ashley/q/valgrind/working/valgrind/memcheck/mc_replace_strmem.c:402
$ addr2line --exe /tmp/a.out 0x4004BF
/tmp/segv.c:3
|