Crash and Error reporting, minidumps
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14.4k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
one common issue for us is people often report bugs that cause their game to crash
but it's hard to extort dumps from users, especially those on inferior platforms
**maybe use breakpad**
breakpad is also superseded by crashpad
on top of that you may want to give socorro a try
to automatically collect and aggregate those crashes
https://github.com/mozilla-services/socorro
I strongly suggest you look into integrating that if you ever start shipping binaries
_Originally posted by @TheJJ in https://github.com/SFTtech/openage/issues/920#issuecomment-336109243_
Probably we want to integrate crashpad and use socorro the server-side, then?
Minidump-upload in c++(breakpad example)
Socorro is a server to accept and process Breakpad crash reports.
Sigaction can get the signal in runtime.
sigaction(SIGSEGV, &handler, NULL)
Contributor guide
No contributing guide indexed for this repository
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
Start with the linked Crashpad repository and Breakpad Linux starter guide, then compare the minidump_upload.cc example with Socorro's server-side requirements. The issue does not name openage files or tests; completion would require defining and documenting an agreed crash-reporting integration path, including collection and aggregation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100