vscode-hxcpp-debug
vscode-hxcpp-debug copied to clipboard
Document compatibility
Versions of relevant products:
- VSCode
- hxcpp
- hxcpp-debugger
Update instructions to point to specific git revs? For hxcpp-debugger at least?
Also check back into #43 once I have a known set of good versions.
FYI, noted in readme: Tested working combo: Haxe 3.4, VSCode 1.8, hxcpp 3.4.69
Tried Haxe 3.4.2, VSCODE 1.12.1, hxcpp git. On launch.json, where it says "type": "hxcpp" there is a warning about "this type is not recognized. install the corresponding debug extension".
When trying to debug with NME the following error appears
Cannot read property 'toLowerCase' of undefined
(I had changed "openfl build windows" to "nme" in the launch.json )
Edit: Commenting https://github.com/jcward/vscode-hxcpp-debug/blob/9d10f079f58bac5479279d40bf95cf4729938e9c/src/Main.hx#L312
and recompiling removes the error, but then nothing happens
Edit2:
Uhh, removing that line makes the defaut "do_disconnect". I just leave it as (value=='true')
(without toLowerCase for now). The application now launches but I don't think the pause and break points are working. Thanks
Edit3:
Not sure why, but I still have the "toLowerCase" error. Seems to be something in the NME tools. in the other hand, Debugging now seems to work if I build the "test openfl" from outside, and in Visual Studio Code only select Debug (without Build) with nme -debug -DHXCPP_DEBUGGER
.
Edit 4: https://github.com/haxenme/nme/issues/453
Hi @madrazo - odd. All that code is doing is taking the args, and splitting them at the = sign, and taking the values on the right.
_runInTerminal
defaults to false. Maybe just remove this line from the args array?
@jcward actually I think that it is another "toLowerCase" somewere else. There is also a javascript function with that name. Do you know how can I access the full logs?
@madrazo I don't use JavaScript in this project, though VSCode is largely javascript. You could turn on the VSCode developer tools, then try to pause on exceptions, then try to run your build.
If you get the error and a stack trace, post it here.