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.

Sign up for GitHub

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

Jump to bottom

Dtrace support #6

Open
mattmacy opened this issue Oct 28, 2018 · 2 comments
Open

Dtrace support #6

mattmacy opened this issue Oct 28, 2018 · 2 comments
Assignees
@mattmacy
Labels
bug Something isn't working Diagnostics
Projects
Kernel Feature Parity
Milestone
Week 51

Comments

@mattmacy
Copy link

Code exists but is broken on POWER9.
@mattmacy mattmacy created this issue from a note in Kernel Feature Parity (To do) Oct 28, 2018
@mattmacy mattmacy self-assigned this Oct 28, 2018
@mattmacy mattmacy added this to the Week 46 milestone Oct 28, 2018
@mattmacy mattmacy added bug Something isn't working Diagnostics labels Oct 29, 2018
@mattmacy mattmacy modified the milestones: Week 46, Week 51 Nov 6, 2018
@gromero
Copy link

gromero commented Apr 22, 2019

@mattmacy Hi! Do you have a reproducer for this issue. At least dtrace -n 'dtrace:::BEGIN { printf("Hello FreeBSD!\n"); }' works for me on a P9 VM. Thank you.

@chmeeedalf
Copy link

How is DTrace broken? I've run plenty of traces and they work fine. The only thing I'm aware of is the CTF data is broken, due to overflow in the type table, and many duplicate type entries. The tracing itself works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mattmacy mattmacy

Labels
bug Something isn't working Diagnostics
Projects
Kernel Feature Parity
  
To do
Milestone
Week 51
Development

No branches or pull requests
3 participants
@chmeeedalf @gromero @mattmacy