[LLVMdev] Heads-up: symbolized stack traces in LLVM/Clang tools crash dumps

Alexey Samsonov vonosmas at gmail.com
Sun Oct 5 22:03:26 PDT 2014

Hi everyone,

I plan to submit http://reviews.llvm.org/D5610 this week. This change
modifies LLVM crash signal handler used in most tools, so that it attempts
to use llvm-symbolizer
<http://llvm.org/docs/CommandGuide/llvm-symbolizer.html> binary and print
function name and file/line information for each stack frame. See review
thread for a specific example of the stack trace printed before and after
this change.

This change is mostly intended to help LLVM/Clang developers: for instance,
now if your debug build of Clang crashes anywhere, you won't have to re-run
it once again under gdb to see the *actual* stack trace.

A couple of notes:
1) This would only work on selected platforms (Linux and OS X are included).
2) If symbolization fails for some reason, signal handler will fall back to
the original behavior.

Please speak up if you have any concerns about this change. Note that if
you have tools that parse the output of LLVM crash reports - you will have
to update them to match the new format.

Alexey Samsonov
vonosmas at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20141005/375f2486/attachment.html>

More information about the llvm-dev mailing list