Dump stack traces on assertion, crash, or general trouble
|Reported by:||nickm||Owned by:|
|Actual Points:||Parent ID:||#11046|
Description (last modified by nickm)
It's so easy to dump stack traces these days!
I have a "backtrace" branch right now that an dump stack traces on assertion failures. It works on glibc/ELF, and on OSX. We should expand it to work on Windows too, and BSD if we can.
Other fixes to make before it's ready:
It should be able to log a stack trace too. It should log the stack trace on an assertion. There should be an option to tell it not to log to the stack_dumps file, perhaps. Perhaps the logfile should be pid-controlled?
- It should support Windows.
It should handle deadly signals (SEGV, etc) as well. It should indicate to the user somehow (if it can) that stuff might be saved to the stack_dumps file. It should have tests.
Change History (18)
comment:10 Changed 17 months ago by nickm
- Resolution set to implemented
- Status changed from needs_review to closed
comment:11 Changed 13 months ago by cypherpunks
comment:13 Changed 13 months ago by nickm
- Resolution implemented deleted
- Status changed from closed to reopened