Taking full dumps

[Omer D]

Hi, 

I'm trying to play with chrome (official google release) on my machine and want to tweak crashpad a little bit. crashpad is defaulted to take small minidumps and I want to have a bigger dump with more information. 

I've noticed that If would have compiled chromium on my machine, I could teak client/crashpad_info.h and configure it to forward the handling of crashes to the system crash reporter.

I haven't found a way to control it with chrome.exe command line and it doesn't seem it reads this value from a file or something. The documentation of crashpad_handler.md doesn't seem to be helpful either in my case.

Is there any simple way to forward official chrome crashes to Windows? or set crashpad to take full dumps?

Thanks.

[Leonard Mosescu]

Crashpad does not have the same knobs as the native Windows minidump writer. What extra information would you like to capture?

--
You received this message because you are subscribed to the Google Groups "Crashpad-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to crashpad-dev...@chromium.org.
To post to this group, send email to crashp...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/crashpad-dev/bda5d6b1-accd-4422-9165-4756d18e42e9%40chromium.org.

[Omer D]

Crashpad generates small minidumps and they don't contain a lot of useful information for analysis.

One useful tool in my toolbox is the command !address of windbg. However, this command returns very minimal amount of data in case of minidump. so for example, you can't see the protection,type and usage of the memory ranges, not to mention getting the contents of the memory pages.

Is there any workaround you can tell me about?

[Leonard Mosescu]

On Windows, Crashpad is supposed to capture the MemoryInfoListStream information. So the first suggestion is to open a Crashpad bug with detailed information about what's missing (with specific examples, ideally attaching a minidump if possible)

I'm not aware of any easy workaround (other than a local Chrome build to disable Crashpad). I created a suggestion bug to add a --disable-crashpad switch.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/crashpad-dev/63190161-4ed6-47e8-8f41-03ebccbe6468%40chromium.org.