-
Notifications
You must be signed in to change notification settings - Fork 16
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
Debugger does not attach (using Docker/Commandbox Image) #66
Comments
Cool, thanks for the repro, that helped out a lot. Small tweak to your config will make this work, it seems that you are having the debugger run on some kind of ephemeral-for-setup-purposes JVM that then kicks off the JVM you actually want to debug. Basically, move jvm args from your docker ENV into to the server.json "jvm" section
Thanks to @jamiejackson for his investigation in #32 (especially for that magic _jdk suffix for the java version). |
@softwareCobbler Thank you! That works with your changes. I have no idea how an "ephemeral-for-setup-purposes JVM" got started and did not intentionally set that up anywhere (maybe some kind of under the hood stuff going on in the docker image?). In any case, thank you for your work on this - I can't live without being able to step through codebases in Lucee.. |
I have a docker container using a commandbox image tagged with jdk11, and I can see luceedebug start up, but when I set a breakpoint and press the debug button to attach in VS Code, the stepper menu panel appears for a second and disappears. The debugger does not attach and none of the breakpoints set work or catch. I cannot find any error output or logs and am not sure how to debug it or figure out why it's not working.
A repo with the code I am running can be found here: https://github.com/BrentGrammer/ModernizeJSApp/tree/Luceedebug
OS: Windows 10
luceedebug VSCode extension version: v2.0.10
.jar path on my machine (in my project folder): ./luceedebug-2.0.14.jar
here is my launch.json
Here is my docker compose yml:
When running
docker compose up
I get the following output:The text was updated successfully, but these errors were encountered: