| << Back to previous view |
|
[QB-2303] add addr2line function on webpage
|
|
| Status: | Open |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 5.1.28 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major |
| Reporter: | wenan li | Assigned To: | Robin Shen |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | 1 week | Time Spent: | Unknown |
| Original Estimate: | 1 week | ||
| Environment: | win7 | ||
| Description |
|
when we get a issue about force close.
we may get backtrace like below. 11-17 14:08:07.615 243 243 I DEBUG : backtrace: 11-17 14:08:07.615 243 243 I DEBUG : #00 pc 0003ddd6 /system/lib/libmediaplayerservice.so (android::MediaPlayerService::Client::MediaPlayerServiceVolumeRampUpThread(void*)+45) 11-17 14:08:07.615 243 243 I DEBUG : #01 pc 0000e58f /system/lib/libutils.so 11-17 14:08:07.615 243 243 I DEBUG : #02 pc 0000d2f8 /system/lib/libc.so (__thread_entry+72) 11-17 14:08:07.615 243 243 I DEBUG : #03 pc 0000d490 /system/lib/libc.so (pthread_create+240) If we want to locate the line num of error source code. we should 1: find the RBS/PBS link by specific Version 2: download symbols library file which should look like DEBUG_SYMBOLS_A700YDZTU0ANK3_CL3259448_QB2966196_REV00_user_low_ship_MULTI_CERT.tgz, more than 600MB 3: find arm-linux-androideabi-addr2line.exe in android NDK, execute below command in cmd arm-linux-androideabi-addr2line.exe -f -e /libmediaplayerservice.so 0003ddd6 should get reslut like below _ZN7android18MediaPlayerService6Client36MediaPlayerServiceVolumeRampUpThreadEPv /home/dpi/qb5_8814/workspace/A7LTE_CHN_TW/android/frameworks/av/media/libmediaplayerservice/MediaPlayerService.cpp:1640 then we know the exactly location of code which cause fc. 4: go to P4 to get the relate code to do further analysis. step 1~4, may take 20 min (depend on network) I think it should have better way. PBS/RBS have this function A, we copy the backtrace LOG to the text field providerd B, webpage should return the result which should show the code caused fc.(file version is the version made this build) may take less than 1 second. please consider the new feature request carefully. addition function 1, continue above progress, if we checked the issue,and have a solution. can we just modify code in webpage and rebuild? 2, can we have some tips on this issue? for example, this issue is cause by SIGSEGV webpage can show some tips about it what does the exactly meaning of SIGSEGV? how to prevent it and show some example. any question, please contact me(ID: wenan.li) BR! |