4 ms·

Reminds me of "Your program shouldn't have bugs in it isn't an acceptable position to take for a debugger", from the rr folks. Unfortunately I can't find the so

Reminds me of "Your program shouldn't have bugs in it isn't an acceptable position to take for a debugger", from the rr folks. Unfortunately I can't find the source of the quote any more, but it stuck in my mind.

Gankra 4y ago
Yeah computing backtraces in a crashreporter is extremely similar to a debugger in that you need a lot of fudge-factor heuristics and fallback modes for known toolchain bugs or common corruptions.
gpm 4y ago
Speaking of the rr folk, they also had the fascinating point that you can reliably generate a "stack trace" by figuring out which `call` instructions were executed with what values (also other jump instructions I suppose), instead of walking the stack. Thereby skipping the whole "parsing the stack is insanely difficult and unreliable" issue.
- glandium 4y ago
  FWIW, that's from pernosco, not rr.
  - gpm 4y ago
    I think it's the same people?
    - db48x 4y ago
      It is. rr records the trace and the Pernosco converts it into a database that can be queried.
khuey 4y ago
You're probably remembering https://pernos.co/blog/tzcnt-portability/ https://pernos.co/blog/tzcnt-portability/