Skip to content
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

Feature Req: Compound config support. #1041

Open
hc2683 opened this issue Jul 31, 2020 · 1 comment
Open

Feature Req: Compound config support. #1041

hc2683 opened this issue Jul 31, 2020 · 1 comment

Comments

@hc2683
Copy link

hc2683 commented Jul 31, 2020

Are there any plans to add support for compound configurations (i.e. as the rest of vscode can do through defining compound configurations in launch.json)? Use case is JNI interfaces; want to launch a java test, and simultaneously launch a GDB C++ debugging instance that attaches to java to allow debugging when we reach C++ code.

Right now the specification of java.test.config outside of launch.json and the automated generation of the java side test config (to correspond to the method that we hit debug on) means we can't define a compound debugging config.

Obvious workaround right now is to have multiple instances of vscode running, and manually attach after launching and hitting a breakpoint on the java side, but would be immensely useful to have this natively supported in vscode-java-test.

@jdneo
Copy link
Member

jdneo commented Aug 1, 2020

@hc2683 Maybe adding a setting to turn on/off persisting the launch configuration into launch.json when executing tests? What do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants