<![CDATA[Child process control]]>I debugging arm program ( on stm32f103c8t6) from npp console with "cmd /c arm-none-eabi-gdb " command .
After send “run” command GDB server enter continuous RUN_MODE .
When i want only end current debug operation and exit RUN_MODE use CTRL+C, but child process complete ending and GDB exiting.

Whereas GDB running from ms-dos console , CTRL+C only ended current debug program and enter HALT_MODE . How can from npp console for this do .

]]>https://community.notepad-plus-plus.org/topic/26750/child-process-controlRSS for NodeThu, 18 Jun 2026 09:12:51 GMTSat, 05 Apr 2025 14:55:16 GMT60<![CDATA[Reply to Child process control on Sat, 05 Apr 2025 23:51:58 GMT]]>@unal-mk ,

I’ve never looked into the Ctrl+C behavior on NppExec. But there are some power-users of NppExec that sometimes read here, and even occasionally the author @Vitalii-Dovgan – so hopefully someone else will be able to help you with that.

]]>https://community.notepad-plus-plus.org/post/100774https://community.notepad-plus-plus.org/post/100774Sat, 05 Apr 2025 23:51:58 GMT<![CDATA[Reply to Child process control on Sat, 05 Apr 2025 23:26:36 GMT]]>@PeterJones
Hi ,
I writing macros with NppExec plugin ( in Portable notepad++ 8.7.6 , 64 bit ) for arm debugging and assing butons using Customize Toolbars plugging for this .
To begin debug, my starter macro run this command “nppexec:: cmd /c arm-none-eabi-gdb $(elf_file) -q” and NppExec console opening at the same time.
After start GDB debug program i can using stepi command for step by step debug , everything is normal up to this point.
If i using “run” command GDB debugger enter continuous RUN_MODE . So NppExec console lock and not respond to any command.
Now i wrote a new macro for cancel GDB continuous RUN_MODE , this macro using “proc_signal ctrl-c” command .
When call this stopper macro nothing happens, NppExec console still locked and not respond . But if i press CTRL+C , cmd and GDB child process completely over.
Try NppConsole plugin but at opening of the notepad++ i get a message saying this plugin is incompatible.

]]>https://community.notepad-plus-plus.org/post/100771https://community.notepad-plus-plus.org/post/100771Sat, 05 Apr 2025 23:26:36 GMT<![CDATA[Reply to Child process control on Sat, 05 Apr 2025 15:45:20 GMT]]>@unal-mk said in Child process control:

How can from npp console for this do .

If I understand correctly, you are using some “console” in Notepad++ to run an external debugger, but something about that console is hijacking the Ctrl+C so that it closes the console, instead of just affecting the external debugger that’s being run.

The specifics of the answer depend on which npp console" you mean. If you mean the plugin literally called “NppConsole”, then Plugins > NppConsole > About takes you to this dialog:
c438ccd7-55c5-462b-bdba-40c350bafa7a-image.png
It has some options for the Ctrl+C handling, and my guess is that maybe one of Ignore or Process normally will do what you want. Your described behavior seems to indicate that you’ve got it set to Restart console, if this is indeed the plugin you are using; but I’m not sure, because I’ve apparently never used Ctrl+C in combination with that plugin’s console (I actually rarely use that plugin at all).

]]>https://community.notepad-plus-plus.org/post/100743https://community.notepad-plus-plus.org/post/100743Sat, 05 Apr 2025 15:45:20 GMT