iovisor / iovisor/bcc

Unable to obtain the complete function call stack of `__memset_avx2_erms`.

Open
#4,996 0 comments 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

When I use stackcount and flamegraph to capture the flame graph of the physical memory allocation function, I cannot obtain the complete function call stack of `__memset_avx2_erms`. Please tell me how to solve it. I have used the -g compilation option.

![image](https://github.com/iovisor/bcc/assets/23352727/6cd33f87-35a7-4da0-af0b-4db362d96337)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the physical memory allocation profile with the mentioned stackcount and flamegraph tools, using the provided image and the __memset_avx2_erms symbol as the focus. Trace how stack collection handles this function and verify the result against a complete call stack; done means the flame graph includes the expected callers.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
observability
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.