-
Notifications
You must be signed in to change notification settings - Fork 21
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
[FR] Support "launch" request for debugging configuration #24
Comments
Every debug target will be different, e.g. for the command line you need to run duk.exe with some flags, for embedded systems you may need to copy files and then maybe even run from a menu. There is an option though, create a task that runs the code on your target, and then in the debug configuration set preLaunchTask this should launch the app and then run the attach debug |
Debug targets might be different, but you usually can launch them e.g. by script, which must be run in a terminal and that's something the debug extension should be able to do. For more complex setup you still have the attach option. But I'll give the pre launch task a try. Thanks. Update yes, a prelaunch task works, however it requires to start the debug session twice, because on first run the debugee just starts, nothing else happens. On second start vscode starts debugging just normally. Once closed I get an error message: |
I agree. And though it's on my list, I haven't had the time yet, sadly. Hopefully I can get to it sooner than later. |
@harold-b sorry for increasing the pressure here, but can you please give that problem a higher priority? Currently I have to start my project 100 times a day (because I'm working on tests which only need a few seconds to run, I fix them and re-run). And every time I start it I have to do it twice (because of the blocking prelaunch task) and have to dismiss the error afterwards. That's highly annyoing and very unproductive. Please consider adding a |
Currently only the "attach" request setting is accepted for debugging a duktape application. It would however be much more convenient to have the debugger also launch the application to debug. Constantly having to manually start the application before starting a debugging run is tiring.
The text was updated successfully, but these errors were encountered: