mirek wrote on Mon, 15 July 2019 13:35

Novo wrote on Mon, 15 July 2019 17:16

mirek wrote on Mon, 15 July 2019 02:17

Novo wrote on Mon, 15 July 2019 06:15

This is not a correct behavior.

There is no correct behaviour. This is not defined anywhere in c++ standard.

Mirek

In this case this is a bug with U++. MemDiagCls shouldn't be a global object. It should be created on stack (by GUI_APP_MAIN or by CONSOLE_APP_MAIN). IMHO.

Then it would not work. Think about all that memory allocated in global objects... (and worse, not in initialization phase).

Instead of MemDiagCls you can put on stack a guard-object, which will detect that its destructor got called and set a flag on MemDiagCls.
IMHO, the problem is fixable ...