Help identifying app exit point

[ryanoneill1970]

We have an odd app that is built from Fortran and C++ under msys64 on Windows and we are using VisualGDB to debug it.

When run normally, the app will incorrectly exit when a window bar is clicked on (no user code is run). Using the debugger we just get an exit logged with a 0 result.

In trying to track this down, running the app (or debugger) as administrator solves the problem.

We’d like to know the call stack just before the app exits, is this possible using VisualGDB?

 

Thanks in advance

 

Ryan

[support]

Hi,

This type of issue is indeed fairly tricky to diagnose. Our best advice would be to try setting breakpoints at _exit(), ExitProcess() and below main() (see the call stack with the backtrace past main option).

[Author]

Posts