search

bgreen0 / google-breakpad

Automatically exported from code.google.com/p/google-breakpad
0 stars 0 forks source link

minidump_stackwalk stack scanning doesn't work #521

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. compile test.cpp
2. generate symbol file
3. run the app, and a minidump file will be written
4. use minidump_stackwalk analysis the minidump file, the stack scanning can't 
find the correct stacktrace.
5. use md2core convert minidump file to core file, use gdb open it, then use 
command "bt", the correct stacktrace will display.

What is the expected output? What do you see instead?
I expect the minidump_stackwalk output can display the second delete source 
line in backtrace.

What version of the product are you using? On what operating system?
google breakpad: revision no.1130
os:centos 64bit 6.3 final

Please provide any additional information below.
result.log: minidump_stackwalk analysis result
test.cpp: source file
dump.core: core file converted from minidump file
test: app
59756a53-7c8f-c2a3-53025606-7ccc4bc9.dmp: minidump file

Original issue reported on code.google.com by qiulin6822@gmail.com on 13 Mar 2013 at 6:34

Attachments:

GoogleCodeExporter commented 9 years ago 
it doesn't look like minidump_stackwalk is picking up your symbols correctly.  
are you putting them in the right directory?

Original comment by wfh@chromium.org on 24 Apr 2014 at 4:14