David Ritter added a comment - 2012-09-17 14:30 Just as an example this data in the XML output: <auxwhat> Address 0x4ade13c is not stack 'd, malloc' d or (recently) free'd </auxwhat> <auxwhat> Uninitialised value was created by a stack allocation </auxwhat> <stack> <frame> <ip> 0x8049D9C </ip> <obj> /build/ritter/tests/core/debug/footest_int </obj> <fn> FooBar::testSplit() </fn> <dir> /nfs/devco/ritter/main/tests/tools/core </dir> <file> footest_int.cpp </file> <line> 180 </line> </frame> </stack> Might result in text in the viewer page for the related error (where the stack trace is) that looks like this: Origin of Uninitialised value was created by a stack allocation: Address 0x4ade13c is not stack'd, malloc'd or (recently) free'd 0x8049D9C: FooBar::testSplit() tests/core/debug/footest_int.cpp:180 This is just my take on how the data could be rendered.

Johannes Ohlemacher added a comment - 2012-09-18 10:32 thanks for the example, i am working on something

Johannes Ohlemacher added a comment - 2012-09-18 13:04 Hi David, i am a bit confused by the two auxwhat elements in your xml output and by the way they are related to each other. Could you post the full xml code of the error?

David Ritter added a comment - 2012-09-18 13:22 I have attached a snippet of our XML output. I trimmed it down to just the entire <error> element for the <auxwhat> block that I included in my first comment.

Johannes Ohlemacher added a comment - 2012-09-18 20:39 Thanks. I added support for those auxiliary information (and for --track-origin option) with version 0.15. Each <auxwhat> element can be followed by a complete stacktrace (with multiple stack frames) and is displayed individually after the regular stacktrace. A summary of the auxiliary information (just the messages, no stacktraces) is shown at the top of the page.