minidump_stackwalk

[wst...@gmail.com]

For some reason after updating to the latest crashpad code when processing minidumps using minidump_stackwalk I'm getting empty output and the following on the console:

./minidump_stackwalk minidump.dmp /path/to/symbols/ > log.txt
2016-03-01 11:20:09: minidump_processor.cc:233: INFO: Processing minidump in file minidump.dmp
2016-03-01 11:20:09: minidump.cc:3255: INFO: Minidump opened minidump minidump.dmp on fd 3
2016-03-01 11:20:09: minidump.cc:3300: INFO: Minidump not byte-swapping minidump
2016-03-01 11:20:09: minidump.cc:3645: INFO: GetStream: type 1197932545 not present
2016-03-01 11:20:09: minidump_processor.cc:516: INFO: Unknown exception reason EXC_BAD_INSTRUCTION / 0x00000001
2016-03-01 11:20:09: minidump.cc:1192: ERROR: MinidumpThread has a memory region problem, 0x0+0x0
2016-03-01 11:20:09: minidump.cc:1386: ERROR: MinidumpThreadList cannot read thread 15/16
2016-03-01 11:20:09: minidump.cc:3668: ERROR: GetStream could not read stream type 3
2016-03-01 11:20:09: minidump_processor.cc:99: ERROR: Minidump minidump.dmp has no thread list
2016-03-01 11:20:09: minidump.cc:3229: INFO: Minidump closing minidump on fd 3
2016-03-01 11:20:09: minidump_stackwalk.cc:451: ERROR: MinidumpProcessor::Process failed

Any idea what is going on here?

[Mark Mentovai]

2016-03-01 11:20:09: minidump.cc:1192: ERROR: MinidumpThread has a memory region problem, 0x0+0x0
2016-03-01 11:20:09: minidump.cc:1386: ERROR: MinidumpThreadList cannot read thread 15/16
2016-03-01 11:20:09: minidump.cc:3668: ERROR: GetStream could not read stream type 3
2016-03-01 11:20:09: minidump_processor.cc:99: ERROR: Minidump minidump.dmp has no thread list

That’s no good. You’ve got a thread with no stack memory. Do you see this consistently?

What was the last version of Crashpad that worked well for you?

We saw something like this before, in https://groups.google.com/a/chromium.org/d/msg/crashpad-dev/rD4FSNiHKF8/G6IUiEL8BQAJ. We never really got to the bottom of it then, but you can follow the steps I suggested to figure out whether this thread really has no stack, or how it should have been reported.

Will Stokes wrote:

--
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/c03e6ef4-06f1-479c-89e7-4f400aece361%40chromium.org.

[wst...@gmail.com]

On Tuesday, March 1, 2016 at 11:29:43 AM UTC-5, Mark Mentovai wrote:
> 2016-03-01 11:20:09: minidump.cc:1192: ERROR: MinidumpThread has a memory region problem, 0x0+0x0
> 2016-03-01 11:20:09: minidump.cc:1386: ERROR: MinidumpThreadList cannot read thread 15/16
> 2016-03-01 11:20:09: minidump.cc:3668: ERROR: GetStream could not read stream type 3
> 2016-03-01 11:20:09: minidump_processor.cc:99: ERROR: Minidump minidump.dmp has no thread list
>
>
> That’s no good. You’ve got a thread with no stack memory. Do you see this consistently?

No, not consistently. I just ran the app from the console to watch standard output and saw:

Illegal instruction: 4

I then processed the uploaded minidump and got the following output:

./stackwalker minidump.dmp symbols > log.txt
2016-03-01 11:40:12: minidump_processor.cc:233: INFO: Processing minidump in file minidump.dmp
2016-03-01 11:40:12: minidump.cc:3255: INFO: Minidump opened minidump minidump.dmp on fd 3
2016-03-01 11:40:12: minidump.cc:3300: INFO: Minidump not byte-swapping minidump
2016-03-01 11:40:12: minidump.cc:3645: INFO: GetStream: type 1197932545 not present
2016-03-01 11:40:12: minidump_processor.cc:516: INFO: Unknown exception reason EXC_BAD_INSTRUCTION / 0x00000001
2016-03-01 11:40:12: minidump_processor.cc:103: INFO: Minidump minidump.dmp has CPU info, OS info, no Breakpad info, exception, module list, thread list, no dump thread, and requesting thread
2016-03-01 11:40:12: minidump_processor.cc:137: INFO: Looking at thread minidump.dmp:0/17 id 0x214353
2016-03-01 11:40:12: minidump.cc:294: INFO: MinidumpContext: looks like AMD64 context
2016-03-01 11:40:12: minidump.cc:294: INFO: MinidumpContext: looks like AMD64 context
2016-03-01 11:40:12: basic_source_line_resolver.cc:230: INFO: Loading symbols for module /Volumes/SnapGene/SnapGene.app/Contents/MacOS/./SnapGene from buffer
2016-03-01 11:40:12: basic_source_line_resolver.cc:354: ERROR: ParseLine failed at 7046 for 15c75
2016-03-01 11:40:12: basic_source_line_resolver.cc:230: INFO: Loading symbols for module /Volumes/SnapGene/SnapGene.app/Contents/MacOS/./SnapGene from buffer
2016-03-01 11:40:12: basic_source_line_resolver.cc:354: ERROR: ParseLine failed at 7046 for 15c75
2016-03-01 11:40:12: basic_source_line_resolver.cc:230: INFO: Loading symbols for module /Volumes/SnapGene/SnapGene.app/Contents/Frameworks/QtCore.framework/Versions/5/QtCore from buffer
2016-03-01 11:40:12: basic_source_line_resolver.cc:354: ERROR: ParseLine failed at 2156 for 8195
2016-03-01 11:40:12: basic_source_line_resolver.cc:230: INFO: Loading symbols for module /Volumes/SnapGene/SnapGene.app/Contents/Frameworks/QtWidgets.framework/Versions/5/QtWidgets from buffer
2016-03-01 11:40:12: basic_source_line_resolver.cc:354: ERROR: ParseLine failed at 2331 for b405

The resulting log has a call stack, but now symbols obviously.


Operating system: Mac OS X
10.10.5 14F1505
CPU: amd64
family 6 model 44 stepping 2
16 CPUs

Crash reason: EXC_BAD_INSTRUCTION / 0x00000001
Crash address: 0x10b3ab6d9

Thread 0 (crashed)
0 SnapGene + 0xad96d9
rip = 0x0b3ab6d9 rsp = 0x5532aa20 rbp = 0x5532ab20
1 SnapGene + 0x2fb5ae
rip = 0x0abcd5af rsp = 0x5532ab30 rbp = 0x5532ab60
2 QtCore + 0x21e4a8
rip = 0x0ca1b4a9 rsp = 0x5532ab70 rbp = 0x5532ac90
3 QtWidgets + 0x291df
rip = 0x0bc391e0 rsp = 0x5532aca0 rbp = 0x5532acf0

I'm in the process of trying to get it to load Qt symbols but now my own symbols have stopped working for some strange reason. :-(

> What was the last version of Crashpad that worked well for you?

I just trashed my copy of Crashpad, depot_tools, and gyp and fetched and compiled the latest stuff from git. I then rebuild my app to make sure the latest crashpad_handler was being used by my application to handle and send off the minidump. So I should be using all the latest and greatest stuff.