Parse Android Chrome dump ( 'dmp0' extension ) file.

130 views
Skip to first unread message

Антон Сорока

unread,
Jul 4, 2013, 9:58:45 AM7/4/13
to google-br...@googlegroups.com
 I have a mobile web application. Currently I am involved into bug fixing process. I've got  a bug with follow issue : at the certain stage of game, on the certain android's device, the Google Chrome browser is crashed. First I've found information at the logCat, that 'fingerprint' has created dump information about crash, and had stored it into /data/data/.../***.dmp0. I haven't permission to this folder, so I rooted device, and fetched it...but when I opened this dump, I couldn't parse it, so I continued my research and now I am here. I am more than sure, that chrome has mistakes of usage GL Context at this certain device(Samsung GT-P5100), but this is stable bug. I want to find way of parse this dump file. I didn't find information here about parsing this android's dump files. I will be appreciate to any useful information. 

Lei Zhang

unread,
Jul 4, 2013, 10:06:05 PM7/4/13
to google-br...@googlegroups.com
The one .dmp0 file I looked at is a minidump with some text headers.
Once you remove the text header, you can read the minidump with
Breakpad's dump file processor.
> --
> You received this message because you are subscribed to the Google Groups
> "google-breakpad-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-breakpad...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

Антон Сорока

unread,
Jul 5, 2013, 5:10:42 AM7/5/13
to google-br...@googlegroups.com
 Could you please explain in detail how should I parse those dump's files?
What software should I download( 'minidump' ? ) and how I could parse those files properly...
Any useful links for your opinion...

David Turner

unread,
Jul 11, 2013, 7:23:38 PM7/11/13
to google-br...@googlegroups.com
You will need the symbol/debug information for the crashed process to get readable data out of a minidump.
See https://code.google.com/p/google-breakpad/wiki/GettingStartedWithBreakpad for a simple explanation.

Since you're talking about Chrome, you won't have this debug information, so you will only be able the very raw content of the minidump, which will probably won't be very useful.

Did you file a bug on crbug.com about your issue? Chrome crashing is a pretty bad thing, so a repro case would ensure this is fixed relatively quickly.



To unsubscribe from this group and stop receiving emails from it, send an email to google-breakpad...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages