How to use stack tracing in blueCFD-Core

[wyldckat]

For blueCFD-Core, a different way for handling stacktracing had to be implemented, because GCC didn't provide it out-of-the-box.

So whenever you get something like this:

        ZN10StackTraceC1Ev [0x705c1465+0x25]
                 module: C:\PROGRA~1\BLUECF~1\ThirdParty-5.x\platforms\mingw_w64GccDPInt32\lib\libstack_trace.dll
        ZN4Foam5error10printStackERNS_7OstreamE [0x11e1c88+0x218]
                 module: C:\PROGRA~1\BLUECF~1\OpenFOAM-5.x\platforms\mingw_w64GccDPInt32Opt\lib\libOpenFOAM.dll
        ZN4Foam6sigFpe13sigFpeHandlerEi [0x11e2af3+0x33]
                 module: C:\PROGRA~1\BLUECF~1\OpenFOAM-5.x\platforms\mingw_w64GccDPInt32Opt\lib\libOpenFOAM.dll
        (No symbol) [0x40684d]
                 module: C:\PROGRA~1\BLUECF~1\OpenFOAM-5.x\platforms\mingw_w64GccDPInt32Opt\bin\chtMultiRegionFoam.exe
        _C_specific_handler [0x7ff853207ff8+0x98]
                 module: C:\WINDOWS\System32\msvcrt.dll
        0_chkstk [0x7ff854af00ef+0x11f]
                 module: C:\WINDOWS\SYSTEM32\ntdll.dll
        RtlRaiseException [0x7ff854a9b474+0x434]
                 module: C:\WINDOWS\SYSTEM32\ntdll.dll
        KiUserExceptionDispatcher [0x7ff854aeec1e+0x2e]
                 module: C:\WINDOWS\SYSTEM32\ntdll.dll
        ZN4FoamdvERKNS_5UListIdEES3_ [0x11894f5+0x75]
                 module: C:\PROGRA~1\BLUECF~1\OpenFOAM-5.x\platforms\mingw_w64GccDPInt32Opt\lib\libOpenFOAM.dll

This is the stack trace that OpenFOAM applications provided by blueCFD-Core will show when they crash and report back where they crashed.

[wyldckat]

Notes:

1. Only when X: is turned on, is when it's possible to get a more detailed stack trace, which is further detailed here: Setting up the work environment

2. Another note is that it looks like that the PDB creation will only work if the PDB helper DLL is available in the Windows software stack... Namely mspdb80.dll or mspdb100.dll would be necessary, but these are only provided with Microsoft Visual Studio and there is no minimal runtime installer that provides it.

3. There are already various examples of how to interpret these stack traces:

   a. https://www.cfd-online.com/Forums/openfoam/199651-interdymfoam-crash.html
   b. GAMG field matrix error #213
   c. ZN10StackTraceC1Ev error #214
   d. Fail to run on blueCFD-Core 2017 #215