-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Capture proc data to be able to generate minidump #156
Comments
That sounds like an excellent feature - thanks for offering to share it back. |
The change is split in two repos, one for the libcrio and one for this repo. Second PR, for the actual core dump handler, is coming soon |
Thanks - I've merged the PR with some additional house keeping around the workflows and released into crates.io as well as tagged in the repo - https://github.com/No9/libcrio/releases/tag/v2.1.0 |
Sorry for this taking more time than necessary. I had some trouble getting the whole feature tested well enough before I wanted to start a PR. I think I got a clean enough solution, so I have created this PR: #157 Please let me know if there is something that you want changed and I'll do that! |
Let me start by saying that this project has helped me bring core dump related stuff out of process and I love it!
The current setup we have is to generate a minidump from a core dump, which we use breakpads
core2md
To be able to configure a proper minidump, some data from the /proc/$pid/ folder is needed. I have forked this project and added the changes needed for us to be able to support this flow. What it does is that it checks for a flag to see if needs to include proc info, if does then these steps are taken:
The process is repeated for every container in that pod.
I would love to contribute back this change into this project, is that something you all would be interested in having?
The text was updated successfully, but these errors were encountered: