Issue 342 in google-breakpad: Error in minidump_stackwalk: MinidumpThread has a memory region problem, 0x0+0x0

[codesite...@google.com]

Status: New
Owner: ----

New issue 342 by nfelsen: Error in minidump_stackwalk: MinidumpThread has a
memory region problem, 0x0+0x0
http://code.google.com/p/google-breakpad/issues/detail?id=342

What steps will reproduce the problem?
1. minidump_stackwalk -m c14a1419-367e-4959-a8ed-4d3fd2091102.dump
2.
3.

What is the expected output? What do you see instead?

expected output:

the regular stackwalk output

What I get:

2009-11-02 14:22:12: minidump_processor.cc:233: INFO: Processing minidump
in file ./name/c1/4a/c14a1419-367e-4959-a8ed-4d3fd2091102.dump
2009-11-02 14:22:12: minidump.cc:3255: INFO: Minidump opened minidump
./name/c1/4a/c14a1419-367e-4959-a8ed-4d3fd2091102.dump on fd 3
2009-11-02 14:22:12: minidump.cc:3300: INFO: Minidump not byte-swapping
minidump
2009-11-02 14:22:12: minidump.cc:1825: INFO: MinidumpModule could not
determine version for C:\Program Files\Orb
Networks\Orb\bin\OrbStreamerClient.exe
2009-11-02 14:22:12: minidump.cc:1825: INFO: MinidumpModule could not
determine version for C:\Program Files\Orb
Networks\Orb\bin\LibOrbStreamer.dll
2009-11-02 14:22:12: minidump.cc:1725: ERROR: MinidumpModule could not
determine debug_file for C:\Program Files\Orb
Networks\Orb\bin\boost_filesystem-vc90-mt-1_35.dll
2009-11-02 14:22:12: minidump.cc:1793: ERROR: MinidumpModule could not
determine debug_identifier for C:\Program Files\Orb
Networks\Orb\bin\boost_filesystem-vc90-mt-1_35.dll
2009-11-02 14:22:12: minidump.cc:1825: INFO: MinidumpModule could not
determine version for C:\Program Files\Orb
Networks\Orb\bin\boost_filesystem-vc90-mt-1_35.dll
2009-11-02 14:22:12: minidump.cc:1725: ERROR: MinidumpModule could not
determine debug_file for C:\Program Files\Orb
Networks\Orb\bin\boost_system-vc90-mt-1_35.dll
2009-11-02 14:22:12: minidump.cc:1793: ERROR: MinidumpModule could not
determine debug_identifier for C:\Program Files\Orb
Networks\Orb\bin\boost_system-vc90-mt-1_35.dll
2009-11-02 14:22:12: minidump.cc:1825: INFO: MinidumpModule could not
determine version for C:\Program Files\Orb Networks\Orb\bin\boost_system-
vc90-mt-1_35.dll
2009-11-02 14:22:12: minidump.cc:1725: ERROR: MinidumpModule could not
determine debug_file for C:\Program Files\Unlocker\UnlockerHook.dll
2009-11-02 14:22:12: minidump.cc:1793: ERROR: MinidumpModule could not
determine debug_identifier for C:\Program Files\Unlocker\UnlockerHook.dll
2009-11-02 14:22:12: minidump.cc:1825: INFO: MinidumpModule could not
determine version for C:\Program Files\Unlocker\UnlockerHook.dll
2009-11-02 14:22:12: minidump.cc:1825: INFO: MinidumpModule could not
determine version for C:\Program Files\Orb
Networks\Orb\bin\Plugins\FFMpegPlugins\FFMpegPlugins.dll
2009-11-02 14:22:12: minidump.cc:1725: ERROR: MinidumpModule could not
determine debug_file for C:\Program Files\Orb
Networks\Orb\bin\Plugins\FFMpegPlugins\avformat-52.dll
2009-11-02 14:22:12: minidump.cc:1793: ERROR: MinidumpModule could not
determine debug_identifier for C:\Program Files\Orb
Networks\Orb\bin\Plugins\FFMpegPlugins\avformat-52.dll
2009-11-02 14:22:12: minidump.cc:1825: INFO: MinidumpModule could not
determine version for C:\Program Files\Orb
Networks\Orb\bin\Plugins\FFMpegPlugins\avformat-52.dll
2009-11-02 14:22:12: minidump.cc:1725: ERROR: MinidumpModule could not
determine debug_file for C:\Program Files\Orb
Networks\Orb\bin\Plugins\FFMpegPlugins\avutil-49.dll
2009-11-02 14:22:12: minidump.cc:1793: ERROR: MinidumpModule could not
determine debug_identifier for C:\Program Files\Orb
Networks\Orb\bin\Plugins\FFMpegPlugins\avutil-49.dll
2009-11-02 14:22:12: minidump.cc:1825: INFO: MinidumpModule could not
determine version for C:\Program Files\Orb
Networks\Orb\bin\Plugins\FFMpegPlugins\avutil-49.dll
2009-11-02 14:22:12: minidump.cc:1725: ERROR: MinidumpModule could not
determine debug_file for C:\Program Files\Orb
Networks\Orb\bin\Plugins\FFMpegPlugins\avcodec-52.dll
2009-11-02 14:22:12: minidump.cc:1793: ERROR: MinidumpModule could not
determine debug_identifier for C:\Program Files\Orb
Networks\Orb\bin\Plugins\FFMpegPlugins\avcodec-52.dll
2009-11-02 14:22:12: minidump.cc:1825: INFO: MinidumpModule could not
determine version for C:\Program Files\Orb
Networks\Orb\bin\Plugins\FFMpegPlugins\avcodec-52.dll
2009-11-02 14:22:12: minidump.cc:1725: ERROR: MinidumpModule could not
determine debug_file for C:\Program Files\Orb
Networks\Orb\bin\Plugins\FFMpegPlugins\swscale-0.dll
2009-11-02 14:22:12: minidump.cc:1793: ERROR: MinidumpModule could not
determine debug_identifier for C:\Program Files\Orb
Networks\Orb\bin\Plugins\FFMpegPlugins\swscale-0.dll
2009-11-02 14:22:12: minidump.cc:1825: INFO: MinidumpModule could not
determine version for C:\Program Files\Orb
Networks\Orb\bin\Plugins\FFMpegPlugins\swscale-0.dll
2009-11-02 14:22:12: minidump.cc:1825: INFO: MinidumpModule could not
determine version for C:\Program Files\Orb
Networks\Orb\bin\Plugins\HTTPOutput\HTTPOutput.dll
2009-11-02 14:22:12: minidump.cc:1192: ERROR: MinidumpThread has a memory
region problem, 0x0+0x0
2009-11-02 14:22:12: minidump.cc:1386: ERROR: MinidumpThreadList cannot
read thread 12/15
2009-11-02 14:22:12: minidump.cc:3668: ERROR: GetStream could not read
stream type 3
2009-11-02 14:22:12: minidump_processor.cc:99: ERROR: Minidump
./name/c1/4a/c14a1419-367e-4959-a8ed-4d3fd2091102.dump has no thread list
2009-11-02 14:22:12: minidump.cc:3229: INFO: Minidump closing minidump on
fd 3
2009-11-02 14:22:12: minidump_stackwalk.cc:473: ERROR:
MinidumpProcessor::Process failed

What version of the product are you using? On what operating system?

trunk as of Oct 9, 2009 but it's still valid with today's trunk (nov 2nd)

Please provide any additional information below.

I attached a dump so you can check on your side (I can't provide the
symbols but it's not required to reproduce the error)
the stack resolution works fine in VisualStudio

Attachments:
c14a1419-367e-4959-a8ed-4d3fd2091102.dump 127 KB

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings