Dump stack and objects on crash for post-mortem debugging
Open
Nobody has claimed this yet.
new feature
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 560
- Avg merge
- 1h 41m
- Merged PRs (30d)
- 3
Description
To aid in debugging crashes it would be very useful to have code which dumped the stack and state of the system to a file to allow for post-mortem debugging. This would allow complex crashes to be fixed, along with one-time crashes such as #134. Is anyone familiar with post-mortem debugging in python? @adamgreen , I heard you might have some knowledge in this area.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by researching Python post-mortem debugging and how pyOCD handles crashes; done means producing a file containing the stack and system state for later debugging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools, embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100