Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

extension: add followExec and followExecRegex options in launch request #3840

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

Draft
Lslightly wants to merge 1 commit into golang:master
base: master
Choose a base branch
Loading
from Lslightly:dap-enable-follow-exec

Conversation

Copy link
Contributor

@Lslightly Lslightly commented Aug 17, 2025
edited
Loading

Add followExec and followExecRegex options in launch request in
launch.json. Before InitializedEvent is sent back from delve, followExec
and followExecRegex will be set in delve. If the program being
debugged spawns a new child process at the beginning and
breakpoints are set in source code line of child process, these
breakpoints will be hit and shown to the user.

Without these two options, although go-delve/delve#4078 provides
delve command to enable follow-exec in console, user have to
manually enable follow-exec in console each time launching the
debug session.

Fixes #3712

Copy link
Collaborator

This PR (HEAD: 2532b54) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/vscode-go/+/696795.

Important tips:

  • Don't comment on this PR. All discussion takes place in Gerrit.
  • You need a Gmail or other Google account to log in to Gerrit.
  • To change your code in response to feedback:
    • Push a new commit to the branch used by your GitHub PR.
    • A new "patch set" will then appear in Gerrit.
    • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
    • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
    • Multiple commits in the PR will be squashed by GerritBot.
  • The title and description of the GitHub PR are used to construct the final commit message.
    • Edit these as needed via the GitHub web interface (not via Gerrit or git).
    • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
  • See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

Copy link
Collaborator

Message from Gopher Robot:

Patch Set 1:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/696795.
After addressing review feedback, remember to publish your drafts!

Copy link
Collaborator

Message from Qingwei Li:

Patch Set 1:

(2 comments)


Please don’t reply on this GitHub thread. Visit golang.org/cl/696795.
After addressing review feedback, remember to publish your drafts!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

add support for debugging child process enabled by delve backend

AltStyle によって変換されたページ (->オリジナル) /