-
Notifications
You must be signed in to change notification settings - Fork 752
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
debug: support delve's rewind command #110
Comments
The rewind option is available in two cases:
Tracked under #1243, which has been fixed.
Dlv-dap does support backend attributes, but we still need to verify that this works end-to-end on Linux. |
I am able to launch with "rr" backend. The trace is generated and the Step Back button shows up. Unfortunately, there appears to be some kind of compatibility issue with rr and my workstation not related to dlv dap - the recording exits before anything runs, so I don't hit any breakpoints and can't test the button itself. @lggomez Could you confirm please that this works for you?
|
@polinasok Is this on main branch? I'm using launch config My setup is the following
|
@lggomez No I don't mean "replay" mode. That one takes a pre-generated file. If you add "rr" backend to any other launch mode it should run and record for you and then replay that recording. |
FYI @rogchap @t-bast who were on the original issue microsoft/vscode-go#1529 |
Change https://golang.org/cl/359398 mentions this issue: |
Updates #110 Change-Id: I820c96bd30bf830fe0d13497f9bcc7f200d8c9bc Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/359398 Trust: Hyang-Ah Hana Kim <hyangah@gmail.com> Run-TryBot: Hyang-Ah Hana Kim <hyangah@gmail.com> TryBot-Result: kokoro <noreply+kokoro@google.com> Reviewed-by: Polina Sokolova <polina@google.com>
@hyangah Could you please verify that rewind buttons works as expected when hitting a breakpoint with the following configuration on Linux?
|
This is a request to add integration to the rewind command in delve. Please see microsoft/vscode-go#1529 for details where there are discussions on the implementation as well as links to past PRs that attempted to add this feature
Corresponding PR in this repo: #89
The text was updated successfully, but these errors were encountered: