Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

eBPF tracing support #239

Open
hariom-qure opened this issue Mar 26, 2024 · 0 comments
Open

eBPF tracing support #239

hariom-qure opened this issue Mar 26, 2024 · 0 comments

Comments

@hariom-qure
Copy link

hariom-qure commented Mar 26, 2024

Linking the original issue here (we use rules_python, where I raised it first): bazelbuild/rules_python#1737

I want to use eBPF to do arbitrary performance profiling of our code, but its not very useful if the python interpreter is not compiled with dtrace and frame pointer support. Without these two, all the information about function names are lost in the stack trace.
The important flags:

  1. --with-dtrace: This flag enables static markers inside python which we can hook into using eBPF (details: https://docs.python.org/3/howto/instrumentation.html)
  2. Enable Frame pointer: -fno-omit-frame-pointer in gcc. This makes sure the information of function names in stack trace is not lost. References: https://www.brendangregg.com/blog/2024-03-17/the-return-of-the-frame-pointers.html
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant