android / android/ndk

[FR] ndk-stack supports parsing the discontinued backtrace

Open
#2,171 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
No language data
Stars
2.3k
Forks
310
PR merge metrics
No merged PRs in 30d

Description

### Description

Currently, the ndk-stack can only parse the first part of the backtraces. Is there any chance to support parsing all backtraces?

The backtrace log:
`--------- switch to crash
08-06 08:10:53.910534 15173 15173 F DEBUG : backtrace:
08-06 08:10:53.910867 15173 15173 F DEBUG : #00 pc 00000000000d0490 /data/app/~~RGD-C1JOEdqoIYumtu8x5g==/com.test.app-MM9zh2ks_WhO-XbYBxDKMA==/lib/arm64/libtest.so (BuildId: b5cf157dc705017edf638c1b08a2314857a2a179)
08-06 08:10:53.910936 15173 15173 F DEBUG : #01 pc 00000000000bdbe0 /data/app/~~RGD-C1JOEdqoIYumtu8x5g==/com.test.app-MM9zh2ks_WhO-XbYBxDKMA==/lib/arm64/libtest.so (BuildId: b5cf157dc705017edf638c1b08a2314857a2a179)
--------- switch to main
08-06 08:10:53.910623 1885 2313 I chatty : uid=1000(system) accessibility_s identical 1 line
08-06 08:10:53.910858 1885 2313 E MegaMars: [ (ContentDescription.java:90)#from ]parse resetView error: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $
08-06 08:10:53.911034 1885 2313 I mars-debug: [ (RootNodeScanner.kt:417)#generateUINodes ]generateUINodes cost: 6 ms
--------- switch to crash
08-06 08:10:53.911039 15173 15173 F DEBUG : #02 pc 00000000000d09cc /data/app/~~RGD-C1JOEdqoIYumtu8x5g==/com.test.app-MM9zh2ks_WhO-XbYBxDKMA==/lib/arm64/libtest.so (BuildId: b5cf157dc705017edf638c1b08a2314857a2a179)
08-06 08:10:53.911129 15173 15173 F DEBUG : #03 pc 00000000000a8f1c /data/app/~~RGD-C1JOEdqoIYumtu8x5g==/com.test.app-MM9zh2ks_WhO-XbYBxDKMA==/lib/arm64/libtest.so (BuildId: b5cf157dc705017edf638c1b08a2314857a2a179)
08-06 08:10:53.911231 15173 15173 F DEBUG : #04 pc 00000000000d0f94 /data/app/~~RGD-C1JOEdqoIYumtu8x5g==/com.test.app-MM9zh2ks_WhO-XbYBxDKMA==/lib/arm64/libtest.so (BuildId: b5cf157dc705017edf638c1b08a2314857a2a179)`

Contributor guide

Open the contributing guide

Research direction

Start with the ndk-stack backtrace parser and reproduce the issue using the log in the description, including its repeated crash-section switches. Done means the parser recognizes and processes all backtrace frames rather than stopping after the first section.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.