flingengine / flingengine/FlingEngine
Create a crash report context
Open
- Dominant language
- C++
- Stars
- 415
- Forks
- 16
- Avg merge
- 18h 53m
- Merged PRs (30d)
- 7
Description
We should have some kind of crash report context which will do something like output the callstack (if possible), the logs, etc so that we can more easily debug what is happening.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by surveying the C++ engine for existing logging and platform-specific crash handling, then determine where a crash-report context could be integrated. Done should mean an agreed implementation that captures a callstack when possible and includes relevant logs for debugging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100