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

proc/gdbserver: clean up rr directory on detach #3570

Merged
merged 1 commit into from
Jan 24, 2024

Conversation

aarzilli
Copy link
Member

We used to autoremove the trace recorded by rr but as a result of
various refactorings done to implement follow exec mode this broke.

Restore the functionality.

Also remove the _fixtures/testfnpos.go file which is autogenerated
during testing.

@derekparker
Copy link
Member

Reflecting on this, it seems like maybe the best user experience would be to add a prompt on detach on whether or not to clean up the trace dir (defaulting to true). It could be to the users benefit to keep that recording around for future debugging.

@aarzilli
Copy link
Member Author

Reflecting on this, it seems like maybe the best user experience would be to add a prompt on detach on whether or not to clean up the trace dir (defaulting to true). It could be to the users benefit to keep that recording around for future debugging.

If we do that we also have to save the executable since the recording is useless without it.

@derekparker
Copy link
Member

Reflecting on this, it seems like maybe the best user experience would be to add a prompt on detach on whether or not to clean up the trace dir (defaulting to true). It could be to the users benefit to keep that recording around for future debugging.

If we do that we also have to save the executable since the recording is useless without it.

That's true. What are your thoughts on conditionally keeping both around?

@aarzilli
Copy link
Member Author

My opinion is that it isn't worth it, there's other ways to permanently make a recording and in an emergency you could always make a copy of both manually if you really needed to. But I don't feel strongly about it.

We used to autoremove the trace recorded by rr but as a result of
various refactorings done to implement follow exec mode this broke.
Restore the functionality.

Also remove the _fixtures/testfnpos.go file which is autogenerated
during testing.
Copy link
Member

@derekparker derekparker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@derekparker derekparker merged commit ef20fbb into go-delve:master Jan 24, 2024
1 of 2 checks passed
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

Successfully merging this pull request may close these issues.

2 participants