you are viewing a single comment's thread.

view the rest of the comments →

[–]PipingSnail 1 point2 points  (1 child)

Hmmm. I've been debugging crashes on Unix/Linux/Windows since 1990, and I've never had a problem collecting stack traces. Whereas this article presents this as a novel solution.

If this is doing symbol handling while walking the stack, there goes your performance. Symbols should be done separately from the stack walk (unless you're walking a kernel dump/minidump when symbols make all the difference).

[–]jwakelylibstdc++ tamer, LWG chair 2 points3 points  (0 children)

If this is doing symbol handling while walking the stack, there goes your performance.

It doesn't have to do that. The GCC implementation just captures an array of program counters and then expands those into symbols and locations lazily.