Re: SIGSEGV SEGV_MAPERR error, unable to find the reason

[Abdul Haseeb]

Use stack trace or kind of log parser to get the stack trace.

You need to have symbols to get the proper stack trace.

Thanks,

Abdul Haseeb

On Tue, Oct 30, 2012 at 4:42 PM, Danny Verloop <dvhtcse...@gmail.com> wrote:

Hi,

My app has been seeing increasing number of crashes for about 2 weeks now and I'm going insane trying to figure it out, it doesn't happen for every user but enough to drop my rating like crazy..

part of dump:

30.10.2012 22:31:45 - I/DEBUG   (13495): pid: 10931, tid: 11087  >>> XXX <<<
30.10.2012 22:31:45 - I/DEBUG   (13495): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaad
30.10.2012 22:31:45 - I/DEBUG   (13495):  r0 00000027  r1 deadbaad  r2 a0000000  r3 00000000
30.10.2012 22:31:45 - I/DEBUG   (13495):  r4 00000001  r5 00000000  r6 48144618  r7 0000a000
30.10.2012 22:31:45 - I/DEBUG   (13495):  r8 00000000  r9 48ff38f0  10 48ff38c8  fp 00000038
30.10.2012 22:31:45 - I/DEBUG   (13495):  ip afd46688  sp 48ff3590  lr afd19239  pc afd15d04  cpsr 68000030
30.10.2012 22:31:45 - I/DEBUG   (13495):  d0  0001000100010001  d1  0001000100010001
30.10.2012 22:31:45 - I/DEBUG   (13495):  d2  00ff00ff00ff00ff  d3  00ff00ff00ff00ff
30.10.2012 22:31:45 - I/DEBUG   (13495):  d4  0000000000000000  d5  0000000000000000
30.10.2012 22:31:45 - I/DEBUG   (13495):  d6  0000000000000000  d7  0000000000000000
30.10.2012 22:31:45 - I/DEBUG   (13495):  d8  0000003800000000  d9  43f0000000000000
30.10.2012 22:31:45 - I/DEBUG   (13495):  d10 0000000042f00000  d11 0000000000000000
30.10.2012 22:31:45 - I/DEBUG   (13495):  d12 0000000000000000  d13 0000000000000000
30.10.2012 22:31:45 - I/DEBUG   (13495):  d14 0000000000000000  d15 0000000000000000
30.10.2012 22:31:45 - I/DEBUG   (13495):  d16 0000000000000000  d17 0104070c131a1f24
30.10.2012 22:31:45 - I/DEBUG   (13495):  d18 0000000000000000  d19 0104070c131a1f24
30.10.2012 22:31:45 - I/DEBUG   (13495):  d20 0000000000000000  d21 0000000000000000
30.10.2012 22:31:45 - I/DEBUG   (13495):  d22 0000000000000000  d23 0000000000000000
30.10.2012 22:31:45 - I/DEBUG   (13495):  d24 0000000000000000  d25 0000000000000000
30.10.2012 22:31:45 - I/DEBUG   (13495):  d26 0000000000000000  d27 282c2f34373c4044
30.10.2012 22:31:45 - I/DEBUG   (13495):  d28 028b4000027f0000  d29 02a3c00002978000
30.10.2012 22:31:45 - I/DEBUG   (13495):  d30 025a8000024e4000  d31 027300000266c000
30.10.2012 22:31:45 - I/DEBUG   (13495):  scr 20000012
30.10.2012 22:31:45 - I/DEBUG   (13495): 

30.10.2012 22:31:45 - I/DEBUG   (13495): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
30.10.2012 22:31:45 - I/DEBUG   (13495): Build fingerprint: \'samsung/YP-G70/YP-G70:2.3.5/GINGERBREAD/UEKI8:user/release-keys\'
30.10.2012 22:31:45 - I/DEBUG   (13495):          #00  pc 00015d04  /system/lib/libc.so (__libc_android_abort)
30.10.2012 22:31:45 - I/DEBUG   (13495):          #01  pc 00013674  /system/lib/libc.so (dlfree)
30.10.2012 22:31:45 - I/DEBUG   (13495):          #02  pc 0001453a  /system/lib/libc.so (free)
30.10.2012 22:31:45 - I/DEBUG   (13495):          #03  pc 000009c4  /system/lib/libstdc++.so (delete)
30.10.2012 22:31:45 - I/DEBUG   (13495):          #04  pc 00052c18  /system/lib/libskia.so (SkBitmapProcShader::SkBitmapProcShader(SkBitmap const&, SkShader::TileMode, SkShader::TileMode))
30.10.2012 22:31:45 - I/DEBUG   (13495):          #05  pc 00070210  /system/lib/libskia.so (SkDraw::drawPosText(char const*, unsigned int, float const*, float, int, SkPaint const&) const)
30.10.2012 22:31:45 - I/DEBUG   (13495):          #06  pc 00072de0  /system/lib/libskia.so (SkDraw::drawBitmap(SkBitmap const&, SkMatrix const&, SkPaint const&) const)

I've added the parts right of the .so files myself, it's the function they are pointing to..

It clearly points to drawbitmap as the root cause, at first I though I was using a Paint object in 2 threads (like http://code.google.com/p/android/issues/detail?id=14267, similar problem and similar stack but I don't use any Paint objects..) I do use BitmapFactory.Options, but they are used in a synchronized block so this is also not the reason (right?).. Is there anything else I can do to figure this out ? The dump trace doesn't give me any more information afaik and Google (the search engine:P) has been helpful in figuring out where the crash comes from but not the root cause..

Any help is greatly appreciated :)

Thanks, Danny

--
You received this message because you are subscribed to the Google Groups "android-platform" group.
To view this discussion on the web visit https://groups.google.com/d/msg/android-platform/-/c3_ofc2wAN0J.
To post to this group, send email to android-...@googlegroups.com.
To unsubscribe from this group, send email to android-platfo...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-platform?hl=en.

[Hai]

maybe you can also search the key words 'fatal signal' to identify
where the issue happened.

[Paul Gardner-Stephen]

Hi Danny,

Are you using any native code?

Are you reading/writing any files on the SDcard?

I ask these questions because mmap() may not work on all sdcard file systems, and MAPERR is the error returned by mmap() when it fails.

Paul.