Add VSCode native debug launcher that attaches to java process. #117
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In my experience on linux searching for "executor" brings up the "Gradle Test Executor" java process of interest when debugging tests hanging in native code.
Note that the sourceFileMap assumes that that wpilib source is installed under $HOME/git/allwpilib. If it isn't, you can still see stack traces, you just won't be able to see the wpilib source.
The "program" location probably needs a windows specific version, maybe with ${env:HOME} replaced with ${env:ALLUSERSPROFILE}?
This was referenced Jul 16, 2024
CoolSpy3
requested changes
Jul 17, 2024
Co-authored-by: CoolSpy3 <55305038+CoolSpy3@users.noreply.github.com>
brettle
deleted the
add-vscode-debug-launcher-that-attaches-to-java-process
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note that this includes PR #114.
Other notes:
In my experience on linux searching for "executor" brings up the "Gradle Test Executor" java process of interest when debugging tests hanging in native code.
The sourceFileMap assumes that that wpilib source is installed under $HOME/git/allwpilib. If it isn't, you can still see stack traces, you just won't be able to see the wpilib source.
The "program" location probably needs a windows specific version, maybe with ${env:HOME} replaced with ${env:ALLUSERSPROFILE} or "C:\Users\Public"?