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

process already being traced? #64

Open
rush24 opened this issue Mar 30, 2018 · 3 comments
Open

process already being traced? #64

rush24 opened this issue Mar 30, 2018 · 3 comments

Comments

@rush24
Copy link

rush24 commented Mar 30, 2018

run rbtrace -p $PID --firehose in MacOS 10.13.2 ruby 2.4.2
@SamSaffron
Copy link
Collaborator

I am very confused about this bug report, can you explain in detail what is happening?

@stakach
Copy link

stakach commented Dec 13, 2018

Can happen when something goes wrong and rbtrace doesn't cleanly exit, there is no way to re-attach to the process, even if the previous instance of rbtrace has been killed

@jeremy
Copy link

jeremy commented Jul 30, 2021

May be the same as #87?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jeremy @SamSaffron @stakach @rush24