Users commonly need to pass a bunch of commands on startup of the debugger. It would be good to be able to do this here, too. I suggest the following option for the task definition (similar to GDB/LMDB extensions):
autorun: an optional array of strings that are executed directly after the start of the debugger as if they would be entered by the user in the debug console.
This actually should also allow to setup attach and remote debugging for any GDB/LMDB (like) extensions.
Users commonly need to pass a bunch of commands on startup of the debugger. It would be good to be able to do this here, too. I suggest the following option for the task definition (similar to GDB/LMDB extensions):
autorun: an optional array of strings that are executed directly after the start of the debugger as if they would be entered by the user in the debug console.This actually should also allow to setup attach and remote debugging for any GDB/LMDB (like) extensions.