How to execute a "final" C code after debugging is stopped in VS Code?

Asked Feb 08 '23 at 20:49

Active Feb 08 '23 at 20:51

Viewed 50 times

When you run C code in Visual Studio Code (on Linux) and stop debugging, the atexit() function is not called.

I can understand that the stop (square red button) in VS Code is similar to kill command so no further code allowed to run.

SigHandler function is not called either, see my older (not answered) question : How to catch CTRL+C inside C Program on VS Code on Linux?

So my question is "How can I accomplish to run code (clean-up, close-up, etc.) after the debugging is ended or program-run-finished manually?

edited Feb 08 '23 at 20:51

asked Feb 08 '23 at 20:49

Cem

You tell your debugger to let your program continue to run, instead of killing it – Marcus Müller Feb 08 '23 at 20:51
Or you can detach the debugger from the process. I believe the backend is `gdb`? It has the `detach` command. – Eugene Sh. Feb 08 '23 at 20:54
Should it matter that you don't clean up gracefully when debugging? You surely won't be using *live* data at that stage? I do realise that installing program updates on a live system can be tricky, but that isn't the place to debug. – Weather Vane Feb 08 '23 at 20:55
Yes, it matters. Because I run some motors and when I stop some motors (by chance) are left in a running state. – Cem Feb 08 '23 at 20:59
um, repower the test rig? Or is *that* a live system? – Weather Vane Feb 08 '23 at 21:21
Tell the debugger to evaluate `exit(0)`. – Eric Postpischil Feb 08 '23 at 21:25
@WeatherVane debugging is a skill too. Hitting red square is not the greatest solution – 0___________ Feb 08 '23 at 23:42
@0___________ but that is what OP has asked. Personally, i would have a data set that is easily set up for a repeatable test, or a test rig that can be reset too. – Weather Vane Feb 08 '23 at 23:44

0 Answers0