-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
RR chaos mode #3670
Comments
It looks like this https://github.com/go-delve/delve/blob/master/pkg/proc/gdbserial/rr.go#L144 line is where the arguments for |
That's replay, record is above in RecordAsync. |
🤦 of course |
@aarzilli Would you accept a PR for this? Do you have a preferred flag name or other mechanism for setting the RR flag? |
That's the problem. The simple way to do this is to add a flag to |
I would prefer to have backend specific For example, I can't use rr without |
Adds two environment variables to configure rr invocations. Fixes go-delve#3670
@firelizzard18 @dmvolod I have made a PR about this using environment variables: #3726 |
@aarzilli That works for me, I should be able to set those via VSCode so that takes care of my use case. |
Adds two environment variables to configure rr invocations. Fixes go-delve#3670
Adds two environment variables to configure rr invocations. Fixes go-delve#3670
Please provide a way to pass the
--chaos
flag to therr
backend. Either by a dedicated flag such as--rr-chaos
or as a general--rr-flags
,--backend-flags
,--backend-opts
, etc.Chaos mode is an extremely useful tool for reproducing weird bugs.
The text was updated successfully, but these errors were encountered: