didi25 / google-breakpad

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

Android platform using printf("%s",1) doesn't get stack trace infomation? #531

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.Just using breakpad under android platform in normal way;
2.To cause core dump with code "printf("%s",1)";
3.

What is the expected output? What do you see instead?
I expected to see a normal stack trace,but it's missed,instead,showed only 
infomation below:
Thread 1
 0  libc.so + 0xb74c
  1  libbinder.so + 0x15fd7
  2  libbinder.so + 0x169b3
  3  libbinder.so + 0x22e9a
  4  libutils.so + 0x1d7eb
  5  libbinder.so + 0x1c0ab
  6  libutils.so + 0x1d321
  7  libutils.so + 0x1d2af
  8  libandroid_runtime.so + 0x3c29f
  9  libandroid_runtime.so + 0x3c27f
 10  libutils.so + 0x1d87f
 11  libutils.so + 0x1d7eb
 12  libc.so + 0x11e02
 13  libc.so + 0x119ce

What version of the product are you using? On what operating system?
The newest by now.

Please provide any additional information below.
Nothing more.

Original issue reported on code.google.com by sonysu...@gmail.com on 10 May 2013 at 2:21

GoogleCodeExporter commented 9 years ago
BTW,What I expect to see is a stack trace with file name and code line 
number,but when using "printf("%s",1),they're missed.

Original comment by sonysu...@gmail.com on 10 May 2013 at 2:24

GoogleCodeExporter commented 9 years ago
Your entire stack is in system libraries. You don't have symbols for those 
system libraries, so you're not getting a useful stack. I don't think there's 
anything Breakpad is doing wrong here. You can pull the libraries from the 
device and run dump_syms against them to get symbols for them, although that 
still might not get you a fully useful stack.

Original comment by ted.mielczarek on 10 May 2013 at 2:38