This adds support for backtrace generation to the llvm-symbolizer markup
filter, which is likely the largest use case.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Do you need to update the docs/SymbolizerMarkupFormat.rst to say that backtrace is now implemented?
Code changes look good to me.
llvm/test/DebugInfo/symbolize-filter-markup-bt.test | ||
---|---|---|
14 | If there is a good place, could be worth an entry in the SymbolizerMarkupFormat or somewhere in the documentation explaining what the X.Y format is. IIUC we'd expect it when there are inlined function(s). | |
61 | If I've interpreted this right, there was some function called second, that probably just called first() so it has been inlined here? Only mention of second that I could find was as an inline function. May be worth a comment as it could help explain the backtrace. |
llvm/test/DebugInfo/symbolize-filter-markup-bt.test | ||
---|---|---|
14 | The markup format does not specify what human-readable output looks like. I think it makes sense for the llvm-symbolizer documentation to describe its output formats, but that should not be conflated with the specification of the markup format. |
If there is a good place, could be worth an entry in the SymbolizerMarkupFormat or somewhere in the documentation explaining what the X.Y format is. IIUC we'd expect it when there are inlined function(s).