69615b3604
This PR aims to add support for rr replay and core actions from the DAP layer. This basically encloses the following:
New launch modes: replay and core
The following modes are added:
replay: Replays an rr trace, allowing backwards flows (reverse continue and stepback). Requires a traceDirPath property on launch.json pointing to a valid rr trace directory.
Equivalent to dlv replay <tracedir> command.
core: Replays a core dump file, showing its callstack and the file matching the callsite. Requires a coreFilePath property on launch.json pointing to a valid coredump file.
Equivalent to dlv core <exe> <corefile> command.
Dependencies
To achieve this the following additional changes were made:
Implement the onStepBackRequest and onReverseContinueRequest methods on service/dap
Adapt onLaunchRequest with the requried validations and logic for these new modes
Use CapabilitiesEvent responses to enable the StepBack controls on the supported scenarios (see dicussion here)
Add the corresponding launch.json support on vs code:
Support for replay and core modes golang/vscode-go#1268
|
||
|---|---|---|
| .. | ||
| dlv_attach.md | ||
| dlv_backend.md | ||
| dlv_connect.md | ||
| dlv_core.md | ||
| dlv_dap.md | ||
| dlv_debug.md | ||
| dlv_exec.md | ||
| dlv_log.md | ||
| dlv_redirect.md | ||
| dlv_replay.md | ||
| dlv_run.md | ||
| dlv_test.md | ||
| dlv_trace.md | ||
| dlv_version.md | ||
| dlv.md | ||
| README.md | ||
Using Delve
You can invoke Delve in multiple ways, depending on your usage needs. Delve makes every attempt to be user-friendly, ensuring the user has to do the least amount of work possible to begin debugging their program.
Refer to the main usage document to further explore commands.