Build a Crash Handler
还没有人认领这个 Issue。
评估
调研方向
首先查看 issue 中链接的 Breakpad、backward-cpp 和 Crashpad 参考资料,然后定义 crash handler 的范围和报告格式。完成内容应包括 singleton 风格的行为、支持多个实例共同提供数据,以及收集堆栈跟踪、机器信息、已安装的库和 core dump,以便稍后进行数据库处理。
由索引模型根据 Issue 内容生成。
描述
Crash Handler/Reporter Proposal
Purpose and Problem
Currently our C++ Tools dont have specific Crash hanlders.
this means that the only Crash data we get are errors of parent tools.
this makes it hard for us to get the data we actually want.
We want to build a custom crash Hanlder that wraps around existing tools to give us the specific data in a specific format for us to Process.
We also want a Database to collect all the reports together to later learn from them.
Implementation
We want a Singleton Style implementation to ensure only one Crash handler exists in a single Application Unit.
Multi instantiation should still add data to the Crash Handler.
What do we Want to catch
- stack trace file (backward-cpp) (minidump's)
- machine info (network, cpu, ram)
- this helps to find out if we have a specific hardware set that causes problems
- installed libs
- this helps us identify if a user has incorrect library installed
- or if we conflict with libs
- Core Dumps
Inspiration / Research
Research
Links
--------------- Repos
----------- Tool Docs
- https://www.robopenguins.com/less-crashy-crashes/
- https://chromium.googlesource.com/crashpad/crashpad/+/master/README.md
- https://chromium.googlesource.com/breakpad/breakpad/
---------------- Infos Write Ups
- https://raygun.com/documentation/language-guides/cpp/crash-reporting/installation/
- https://stackoverflow.com/questions/3899870/how-to-print-a-stack-trace-whenever-a-certain-function-is-called/54365144#54365144
- https://www.robopenguins.com/core-dumps/
- https://www.boost.org/doc/libs/master/doc/html/stacktrace/getting_started.html#stacktrace.getting_started.handle_terminates
Inspiration
we can take inspiration by what side fx Houdini is doing with there info section.
- 主要语言
- C++
- 星标
- 0
- 派生
- 2
- 平均合并
- 4 天 7 分钟
- 30 天内合并 PR
- 3
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
ynput/ayon-cpp-dev-tools 的其他 Issue
-
CMake Presets 未关闭
难度 5/5 一周以上 新手友好度 25/100
-
难度 5/5 一周以上 新手友好度 25/100
查看 ynput/ayon-cpp-dev-tools 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 70/100
google/libultrahdr#485 ·
-
难度 2/5 1-3 小时 新手友好度 75/100
godotengine/godot#123776 ·
-
bug
难度 1/5 1 小时以内 新手友好度 60/100
-
good first issue
难度 1/5 1 小时以内 新手友好度 90/100
-
good first issue
难度 2/5 1-3 小时 新手友好度 75/100
ros2/common_interfaces#344 ·