Breakpad test under x86_64 Linux doesn't show full trace

[GoogleCodeExporter]

Hi,

I checked out breakpad rev 791 (latest), compiled with default options, and 
tested using the example on 
http://code.google.com/p/google-breakpad/wiki/LinuxStarterGuide

When I do a minidump_stackwalk of the generated dump file, the output is very 
limited, and I also get the following line in the output:
2011-06-30 15:31:52: minidump_processor.cc:116: INFO: Minidump 
/tmp/4fa2aaf5-1f61-885d-48faf566-51bd9608.dmp has CPU info, OS info, no 
Breakpad info, exception, module list, thread list, no dump thread, and 
requesting thread

I compiled the test app using:
g++ test.cpp src/client/linux/libbreakpad_client.a -Isrc -o test -g
And I checked that test.sym had FILE and FUNC lines in it (it did).

Attached is the full output of the process including the source of the test 
application. My understanding is that I should get a better stack trace with 
more information (comparable to GDB output). If I am wrong, or this is only 
true under windows, please let me know.

Thanks
-Keith Poole

What steps will reproduce the problem?
1.
2.
3.

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

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

Please provide any additional information below.

Original issue reported on code.google.com by plat...@gmail.com on 30 Jun 2011 at 7:45

Attachments:

• BreakpadTest.txt

[GoogleCodeExporter]

Sorry for the extra bits left at the end of the issue.

Here is the symbol file too.

Original comment by plat...@gmail.com on 30 Jun 2011 at 7:48

Attachments:

• test.sym

[GoogleCodeExporter]

This output looks fine to me. You're getting a full stack trace up to start, 
which is exactly what I'd expect. What more information would you want? 
Breakpad does not currently support showing parameters and local variables, 
FWIW. There is a md2core utility you can try that should give you a core file 
you can load in gdb:
http://code.google.com/p/google-breakpad/source/browse/#svn/trunk/src/tools/linu
x/md2core

Original comment by ted.mielczarek on 31 Aug 2011 at 4:22

• Changed state: Invalid

[GoogleCodeExporter]

Hi,

Thanks for your response.

I had misunderstood the level of output I was supposed to get due to what I had 
been told.

Thanks for the point to md2core too!

Regards,
Keith

Original comment by plat...@gmail.com on 31 Aug 2011 at 4:38