@PeterJones
Which debugger did you use?
The problem with all of them is—to quote the DAP specification
Since launching is debugger/runtime specific, the arguments for this request are not part of this specification.
figuring out how to start them.
I do hope that they all have one thing in common: that they expect this as a valid JSON message, which I define as launch_args.
I tried it using the link from @rdipardo, but unfortunately it didn’t work properly. I was able to run through my simple test code step by step, but the variables weren’t returned. That might be due to my configuration or setup, though.
@lycan-thrope
Yes, as long as the debugger supports dap there is a chance that it will work with this client.
Note that all dialog boxes are Scintilla controls and are not protected by the “Read-only” setting. However, this should not be a problem, with the exception of the Breakpoint View, where the client receives information about which breakpoints are currently set. The markers in the source code—currently only in the active document—are removed after the debugging session stops, but they remain in the breakpoint view so they can be reused in a later debugging session.
The exception, of course, is if I click on an already set breakpoint again; then it is also deleted, and of course if I select and delete something in the breakpoint view…
Just for reference the config I used for the linked perl-dap
[perl]
debugger = "C:/WHATEVER_DIR/perl-dap.exe"
debugger_args = ["--stdio"]
mode = "io"
# debugger_args = ["--socket", "--port", "13603"]
# mode = "tcp"
# host = "127.0.0.1"
# port = 13603
env = {
PATH="C:/compilers/strawberry-perl-5.42.2.1/perl/bin",
}
launch_args = '''{
"program": "C:/repos/nppdebugger/tests/debuggees/perl/test.pl",
"cwd": "C:/repos/nppdebugger/tests/debuggees/perl",
"perlPath": "C:/compilers/strawberry-perl-5.42.2.1/perl/bin"
}'''
