iovisor / iovisor/bcc

stackcount return *blank* stack.

Open
#3,891 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
22.7k
Forks
4.1k
Avg merge
10d 4h
Merged PRs (30d)
3

Description

I run the command below in my Android device:
```
python stackcount -p 22119 /apex/com.android.runtime/lib64/bionic/libc.so:memset
```

There're many records without any stack information.
I think even it is using FP to unwind the stack, at least the first frame stack with 'memset' should be shown. Any idea on this issue? Thanks in advance!
```
b'memset'
b'[unknown]'
310

311

322

433

b'memset'
b'MterpInvokeVirtual'
b'mterp_op_invoke_virtual'
b'art::interpreter::Execute(art::Thread*, art::CodeItemDataAccessor const&, art::ShadowFrame&, art::JValue, bool, bool) (.llvm.8678274965593772940)'
b'artQuickToInterpreterBridge'
b'art_quick_to_interpreter_bridge'
564

b'memset'
b'[unknown]'
652

1059

1205

17162

31876
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Begin with the stackcount entry point and reproduce the reported invocation against /apex/com.android.runtime/lib64/bionic/libc.so:memset on Android, comparing records containing only [unknown] with complete samples. Trace the unwinding path and verify the expected first-frame behavior; done means the blank-stack cases are explained and the intended output is tested.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, linux, python
Domain
observability, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.