mirror of https://github.com/go-delve/delve.git synced 2025-11-02 04:36:29 +08:00

Files

Archana Ravindar 89123a0000 pkg/terminal,service/debugger: Support to add a new suboption --follow-calls to trace subcommand (#3594 )

* rebasing on master to implement --followcalls

* in progress changes to enable --followcalls

* rebase to master: modified function to add children to funcs array

* modify main traversal loop

* added tests to check different scenarios

* added tests to check different scenarios

* added tests to check different scenarios

* add test to check for overlapping regular expression

* modified type of strings array as a return only

* changed depth to a simple integer instead of a global map

* avoid calling traverse on recursive calls

* Added tests for various call graphs to test trace followfuncs

* Added tests for various call graphs to test trace followfuncs

* Added tests for various call graphs to test trace followfuncs

* made auxillary changes for build to go through for new option follow-calls

* Add support to print depth of the function calls as well

* Added two sample output files for checking

* Bypass morestack_noctxt in output for verification testing

* Corrected newline error by adding newlines only if the line does not match morestack_noctxt

* Added more tests

* Cleanup

* Updated documentation

* fixed error message in fmt.Errorf

* Fixed result of Errorf not used error

* Addressing review comments to fix depth reporting and other issues

* dont invoke stacktrace if tracefollowcalls is enabled, compute depth from main regex root symbol than main.main

* Addressing a part of review comments

* Added changes to allow deferred functions to be picked up for tracing

* Fix issue to avoid printing stack for a simple trace option

* Moving most tests to integration2_test.go and keeping only one in dlv_test.go

* Moving most tests to integration2_test.go and keeping only one in dlv_test.go

* Adding panic-defer test case

* Moved rest of the tests to integration2_test.go

* addressing review comments: folding Functions and FunctionsDeep, reducing branches by using depth prefix, wrap using %w and other comments

* Optimize traversal and parts of printing trace point function and modify trace output layout
and adjust tests accordingly

* Resolved error occurring due to staticcheck

* Implemented traversal algorithm using breadth first search

* Addressing review comments on the breadth first search implementation and
other comments

* Inline filterRuntimeFuncs and remove duplicate initialization

2024-06-12 12:35:48 -07:00

dlv_attach.md

cmd/dlv: support unix domain sockets (#3655 )

2024-02-07 11:04:45 -08:00

dlv_backend.md

proc/gdbserial: add environment variables to configure rr invocation (#3726 )

2024-05-24 11:33:23 -07:00

dlv_connect.md

cmd/dlv: support unix domain sockets (#3655 )

2024-02-07 11:04:45 -08:00

dlv_core.md

cmd/dlv: support unix domain sockets (#3655 )

2024-02-07 11:04:45 -08:00

dlv_dap.md

cmd/dlv: support unix domain sockets (#3655 )

2024-02-07 11:04:45 -08:00

dlv_debug.md

cmd/dlv: support unix domain sockets (#3655 )

2024-02-07 11:04:45 -08:00

dlv_exec.md

cmd/dlv: support unix domain sockets (#3655 )

2024-02-07 11:04:45 -08:00

dlv_log.md

cmd/dlv: support unix domain sockets (#3655 )

2024-02-07 11:04:45 -08:00

dlv_redirect.md

cmd/dlv: support unix domain sockets (#3655 )

2024-02-07 11:04:45 -08:00

dlv_replay.md

cmd/dlv: support unix domain sockets (#3655 )

2024-02-07 11:04:45 -08:00

dlv_run.md

cmd/dlv: support unix domain sockets (#3655 )

2024-02-07 11:04:45 -08:00

dlv_test.md

cmd/dlv: support unix domain sockets (#3655 )

2024-02-07 11:04:45 -08:00

dlv_trace.md

pkg/terminal,service/debugger: Support to add a new suboption --follow-calls to trace subcommand (#3594 )

2024-06-12 12:35:48 -07:00

dlv_version.md

cmd/dlv: support unix domain sockets (#3655 )

2024-02-07 11:04:45 -08:00

dlv.md

Documentation,cmd/dlv: clean up command line usage help (#3395 )

2023-08-09 10:37:55 -07:00

README.md

terminal: send large output to pager (#3060 )

2022-08-17 09:02:53 +02:00

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.

The available commands can be grouped into the following categories:

Specify target and start debugging with the default terminal interface:
Trace target program execution
- dlv trace [package] <regexp>
Start a headless backend server only and connect with an external frontend client:
- dlv --headless <command> <target> <args>
  - starts a server, enters a debug session for the specified target and waits to accept a client connection over JSON-RPC or DAP
  - <command> can be any of debug, test, exec, attach, core or replay
  - if --headless flag is not specified the default terminal client will be automatically started instead
  - compatible with dlv connect, VS Code Go, GoLand
- dlv dap
  - starts a DAP-only server and waits for a DAP client connection to specify the target and arguments
  - compatible with VS Code Go
  - NOT compatible with dlv connect, GoLand
- dlv connect <addr>
  - starts a terminal interface client and connects it to a running headless server over JSON-RPC
Help information

The above list may be incomplete. Refer to the auto-generated complete usage document to further explore all available commands.

Environment variables

Delve also reads the following environment variables:

$DELVE_EDITOR is used by the edit command (if it isn't set the $EDITOR variable is used instead)
$DELVE_PAGER is used by commands that emit large output (if it isn't set the $PAGER variable is used instead, if neither is set more is used)
$TERM is used to decide whether or not ANSI escape codes should be used for colorized output
$DELVE_DEBUGSERVER_PATH is used to locate the debugserver executable on macOS