How to find a location when there is a segment error on Android

Source: Internet
Author: User

How to find a segment error when Android appears, such as log:

2196  on- Geneva  A: the:01.090F/LIBC (1309): Fatal Signal One(SIGSEGV) at0x00000000(code=1), Thread1388(Surfaceflinger)2197  on- Geneva  A: the:01.210I/debug (1307): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***2198  on- Geneva  A: the:01.210I/debug (1307): Build fingerprint:'Android/4.2/bld.pad-706.b77.tl7689.nusmartqa-user/eng. 20140613.152301/dev-keys'2199  on- Geneva  A: the:01.220I/debug (1307): Revision:'0'2200  on- Geneva  A: the:01.220I/debug (1307): PID:1309, Tid:1388, Name:surfaceflinger >>>/system/bin/surfaceflinger <<<2201  on- Geneva  A: the:01.220I/debug (1307): Signal One(SIGSEGV), code1(Segv_maperr), fault addr000000002202  on- Geneva  A: the:01.250I/debug (1307): R0 40c223c0 R100000000R2 411f8d88 R3 40c223c02203  on- Geneva  A: the:01.250I/debug (1307): R4 411F8D40 R5 411f8c88 R6 411F8D50 R7000000002204  on- Geneva  A: the:01.250I/debug (1307): R8 40c1be18 R9 4098ddd8 SL00000000FP 40c1be202205  on- Geneva  A: the:01.260I/debug (1307): IP ffffffff SP 4098ddb8 LR00000000pc 405a9bd8 CPSR 200f00102206  on- Geneva  A: the:01.260I/debug (1307): D00000000000000000D100000000000000002207  on- Geneva  A: the:01.260I/debug (1307): D20000000000000000D300000000000000002208  on- Geneva  A: the:01.260I/debug (1307): D4 74666f7320797261 d5 79616d20657261772209  on- Geneva  A: the:01.260I/debug (1307): D66465737520656220D7 736120796c6e6f202210  on- Geneva  A: the:01.260I/debug (1307): D80000000000000000D900000000000000002211  on- Geneva  A: the:01.260I/debug (1307): D100000000000000000D1100000000000000002212  on- Geneva  A: the:01.260I/debug (1307): D120000000000000000D1300000000000000002213  on- Geneva  A: the:01.260I/debug (1307): D140000000000000000D1500000000000000002214  on- Geneva  A: the:01.260I/debug (1307): D16 01830b3b09000003 D1700000000000000002215  on- Geneva  A: the:01.260I/debug (1307): D18 419e264d78000000 D1900000000000000002216  on- Geneva  A: the:01.260I/debug (1307): d200000000000000000D2100000000000000002217  on- Geneva  A: the:01.260I/debug (1307): D220000000000000000D2300000000000000002218  on- Geneva  A: the:01.260I/debug (1307): D240000000000000000D2500000000000000002219  on- Geneva  A: the:01.260I/debug (1307): D260000000000000000D2700000000000000002220  on- Geneva  A: the:01.260I/debug (1307): D280000000000000000D2900000000000000002221  on- Geneva  A: the:01.260I/debug (1307): D300000000000000000D3100000000000000002222  on- Geneva  A: the:01.260I/debug (1307): SCR000000102223  on- Geneva  A: the:01.260I/debug (1307):2224  on- Geneva  A: the:01.260I/debug (1307): BackTrace:2225  on- Geneva  A: the:01.260I/debug (1307):     #xxPC 00071bd8/system/lib/libmali.so2226  on- Geneva  A: the:01.260I/debug (1307):     # onPc00072294/system/lib/libmali.so (mali_common_ds_consumer_release_ref_count_change+ the)2227  on- Geneva  A: the:01.260I/debug (1307):     # GenevaPC 0007140c/system/lib/libmali.so2228  on- Geneva  A: the:01.260I/debug (1307):     #GenevaPC 0007af28/system/lib/libmali.so2229  on- Geneva  A: the:01.260I/debug (1307):     #GenevaPC 0000e194/system/lib/libc.so (__thread_entry+332)2230  on- Geneva  A: the:01.260I/debug (1307):     # toPC 0000dc9c/system/lib/libc.so (pthread_create+172)2231  on- Geneva  A: the:01.260I/debug (1307):2232  on- Geneva  A: the:01.260I/debug (1307): Stack:2233  on- Geneva  A: the:01.260I/debug (1307): 4098dd78 411df348 [Heap]2234  on- Geneva  A: the:01.270I/debug (1307): 4098dd7c 405b187c/system/lib/libmali.so2235  on- Geneva  A: the:01.270I/debug (1307): 4098dd80000000012236  on- Geneva  A: the:01.270I/debug (1307): 4098dd84 411df298 [Heap]


Need to see which problem, need to use a tool to locate, the following methods:

 out 00072294

Finish.

How to find a location when there is a segment error on Android

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.