vscode-hxcpp-debug icon indicating copy to clipboard operation
vscode-hxcpp-debug copied to clipboard

Published 20 hours ago • verified publisher icon jcward

Launch with breakpoints - windows

Open hoseyjoe opened this issue 7 years ago • 4 comments

I tried 1.10 and 1.11 of vscode and debugger crashes when launching application. vs insider release works though and did for 1.11? Not sure if this is a debugger issue or vscode-hxcpp-debug issue? I mention it if anyone else runs into same

I haven't really tested it but it isn't crashing on launch

hoseyjoe avatar Apr 06 '17 18:04 hoseyjoe

I just downloaded VSCode 1.11 for Linux 64-bit, and tested the test cli app, with hxcpp 3.4.69, haxe 3.4, and vscode-hxcpp-debugger (latest from git, aka 9d10f07), and it was working. Did you git pull and rebuild the debug adapter with haxe build-<platform>.hxml? What platform are you on, and what kind of app are you running (cli / graphical) / what are your launch.json parameters? What does the end of your /tmp/adapter.log file say after the crash?

jcward avatar Apr 06 '17 19:04 jcward

I just discovered removing all breakpoints allows it to run without issue...If I add 1 breakpoint then I get the below. So insider working was a red herring. I probably had a breakpoint in an obscure .hx file that I had forgot about. Anyways

I can add breakpoints after launch but if they exist before launch then I get the error

VSCode 1.11.1 hxcpp 3.4.80 haxe 3.4.2 vscode-hxcpp-debugger git sync and rebuild Windows 10 I am graphical using NME 6.07

1491956974.573: Reading 89 bytes... 1491956974.573: {"command":"setExceptionBreakpoints","arguments":{"filters":[]},"type":"request","seq":4} 1491956974.573: Got command: setExceptionBreakpoints 1491956974.573: ====== UNHANDLED COMMAND: setExceptionBreakpoints

hoseyjoe avatar Apr 12 '17 00:04 hoseyjoe

I get the exact same issue with a hxWidgets application (same happened with test cli), setting a break point before launch causes the debugger to die. Setting them after launch seems to be fine.

@hoseyjoe where do you see those log lines you pasted? Im happy to try and sort this out, but unsure the best way to debug it - those log likes look like a good start.

ianharrigan avatar Jun 29 '17 17:06 ianharrigan

I believe that come from the plugin. I believe I found my log at c:/tmp/adapter.log but I am not seeing anything there currently

hoseyjoe avatar Jun 30 '17 20:06 hoseyjoe