-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
add stack traces to trace.py #621
Comments
Oh yeah, could be very useful, instead of poking around with a debugger. I think in terms of a timeline, I would like things to happen in this order:
That's my list for the next few weeks I think :) I could also move forward with 2, 4, and 5 to get unblocked and add USDT support later. What do you think? |
Sounds good. I'll look at getting the (1) code we already have integrated. |
@brendangregg I think this can be closed now with @palmtenor 's PR #712. It's not the |
Yes, we can close it, thanks @palmtenor ! And if -KU gets too annoying, we can always add "-s" as an alias for "-KU". |
Would be useful to have a "-s" to print stack traces.
When used on user-level probes, it would only print the user stack trace. When used on kernel, it could print both.
I did do this for kprobe/uprobe in perf-tools using ftrace, which proved very useful.
https://github.com/brendangregg/perf-tools/blob/master/examples/kprobe_example.txt#L302
The text was updated successfully, but these errors were encountered: