Kill C++ application in terminal, destructor not called?

Asked May 03 '18 at 12:51

Active May 03 '18 at 12:51

Viewed 510 times

I'm running a C++ application from a Linux terminal. This application allocates shared memory (using Boost Interprocess).

If I kill the application (Ctrl + c) in the terminal I was expecting a destructor to be called. However, it's not, leaving my shared memory still allocated. Therefore when I go to run again, instead of the shared memory being re-created, the existing memory state is opened. This is undesirable.

Is there a way to get the destructor to be called upon cancelling the application in the terminal?

asked May 03 '18 at 12:51

user997112

29,025
43
182
361

1

Capturing a key stroke and then gracefully exiting could be an option. – Neijwiert May 03 '18 at 12:53
1

You might want to check this SO [How can I catch a ctrl-c event? (C++)](https://stackoverflow.com/questions/1641182/how-can-i-catch-a-ctrl-c-event-c) – CannedMoose May 03 '18 at 12:53
You can *catch* the signal generated by `Ctrl-C` and clean up nicely. – Some programmer dude May 03 '18 at 12:54
@Someprogrammerdude you mean literally try{....} catch(std::exception& e){}? – user997112 May 03 '18 at 12:59
you can set a callback with atexit – Tyker May 03 '18 at 13:01
@user997112 no you can't catch signal like that just exeptions – Tyker May 03 '18 at 13:01
`SIGKILL` cannot be caught. Also, why do you think memory is still allocated after your app got killed? – Andrejs Cainikovs May 03 '18 at 13:04
Ok, I read the question once again. `Ctrl+C` raises `SIGINT`, which can be caught on the app side to do some cleanup. – Andrejs Cainikovs May 03 '18 at 13:06
No, it's not exceptions. Do some searching for *POSIX signals*. – Some programmer dude May 03 '18 at 13:07
@AndrejsCainikovs I can tell the shared memory still exists because when I re-run the program, it checks whether it already exists and reports it. – user997112 May 03 '18 at 13:27

Kill C++ application in terminal, destructor not called?

0 Answers0