Adding an in-place core to minidump processor

[kuzaxak]

I'm working on collecting coredumps, and your project is a great start, but we would like to have a minidump as a result. I've got my PoC based on goblin and rust-minidump working quite well.

Do you think it is something that would fit into this project? I implemented it under a feature flag in core-dump-composer.

If so, I will open a PR.

The goal is to analyse the received coredump, access the memory pages, and produce a meaningful minidump with extra information such as a full stacktrace with recovered function args to handle it via Sentry or any other tool.

This eliminates the need for heavy post-processing, as a full coredump contains too much sensitive information.

CC @No9

[kuzaxak]

I see some discussions happened before here

My main motivation is similar. Since we have exe, we can produce a full minidump, which is much lighter and contains only the necessary info: stacktrace, registries, and selected memory areas.

The final result can be uploaded and processed as a cloud event or uploaded to S3.

Probably, this is not the approach you have for this project, but it is worth discussing with you.