Help with Indirect Memory Collection in Crashpad Minidumps

18 views
Skip to first unread message

Nikola Janevski

unread,
Oct 23, 2025, 1:57:07 PMOct 23
to Crashpad-dev
Hi All,

I'm trying to generate a minidump that includes indirectly referenced memory using Crashpad. Here’s what I’ve done so far:
  • Created a process that registers itself with the crash handler, with indirect memory collection enabled.
  • The process starts multiple threads that allocate memory.
  • The process crashes as intended.
  • However, the minidump size remains unchanged, and I don’t see additional memory included.
I based my code on the Crashpad test here:
https://chromium.googlesource.com/chromium/src/+/edd9c5a2a6356288d596cbc623fa52b4fe124e65/third_party/crashpad/crashpad/snapshot/win/crashpad_snapshot_test_image_reader.cc

However, even in these tests, I don’t see the minidump size or its contents being examined. The only relevant line seems to be:

crashpad::CheckedWriteFile(out, &c, sizeof(c));

But this looks like it just logs some info.

My questions:
  1. Can anyone clarify how indirect memory collection is supposed to work in Crashpad?
  2. How can I ensure that indirect memory is actually collected in the minidump?
  3. What should I look for in the minidump file to confirm that this feature is working?
Thank you for any insights!

Best,
Nikola
Reply all
Reply to author
Forward
0 new messages