On Apr 30, 1:22 pm, Mariano Kamp <[email protected]> wrote: > I am wondering if there is any way to debug a SIGSEV? I have not much > experience with those native crashs. This issue only seems to happen with > the HTC Incredible and I would at least guess that my Java code cannot be > the actual cause, but maybe there is something I can do to avoid triggering > it? [...] > 04-30 15:33:23.514 D/dalvikvm( 1263): GC freed 10573 objects / 916872 bytes > in 64ms > 04-30 15:33:23.534 E/webcoreglue( 1263): The real object has been deleted > 04-30 15:33:23.634 I/DEBUG ( 57): *** *** *** *** *** *** *** *** *** > *** *** *** *** *** *** *** > 04-30 15:33:23.634 I/DEBUG ( 57): Build fingerprint: > 'verizon/inc/inc/inc:2.1-update1/ERE27/161493:user/release-keys' > 04-30 15:33:23.634 I/DEBUG ( 57): pid: 1263, tid: 1264 >>> com.newsrob > <<<
Since it's not a Google build I can't decode the stack trace. If you have an APK and series of steps that reproduces the problem reliably, post a bug on b.android.com with the APK attached. If we can make it happen on one of our devices we can dig further. If not, it may be specific to the Incredible and you will have to work with HTC. Based on the log message and the library list it looks like it could be a libskia (graphics library) problem. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
