-
Notifications
You must be signed in to change notification settings - Fork 42
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
Ustack call yield enexpected result #19
Comments
Hello, If anyone sees this I'd like to try and understand if we could ever expect something here. I'm a very frequent user of DTrace on macOS and bringing my scripts that rely on ustack() over is completely impossible since 99% of the stacks end up not displaying. Some of them do so I know that pdb downloading and loading is wired correctly which makes it all the more frustrating. Thanks for your time. |
@benoitgillet Looks like you're using @OlivierLi Could you give me a sample script and what possible output you see? |
The issue has been recognized. I will start working on a fix soon. |
Great to hear! Thanks for looking into this. For reference for now the two scripts I'm looking to adapt are here with one more to come that I haven't pushed. https://source.chromium.org/chromium/chromium/src/+/main:tools/mac/power/dtrace_scripts/ |
Trying to use a prob with a ustack() call, i encounter the following behavior :
I would expect a stack trace with multiple lines
Following, i put the prob i use
$dtrace -s this_file -c your_program
The text was updated successfully, but these errors were encountered: