Handling of application crashes

Discussion forum about all things Team Developer 7.x
Uwe van der Horst
Site Admin
Site Admin
Germany
Posts: 479
Joined: 05 Mar 2017, 14:21
Location: Wetter (Ruhr), Germany

Handling of application crashes

Post by Uwe van der Horst » 19 May 2020, 09:37

Hi all,

occasionally, our customers report crashes that are not reproducible.

I know the option to use profiling (very helpful).

https://wiki.tdcommunity.net/index.php/ ... _Profiling

In TD 7.2 I find another option that could be helpful - minidumps
Windows minidump: New options to generate minidump files if a crash occurs in a Win32 application. This can be turned on using –minidump command line option,or by setting an environment variable TD_MINIDUMP to 1, ON or YES. Once enabled, a minidump file will be created in the same directory as the application executable in the format <exe-name>-yyyyMMdd-HHmmss.dmp. These dump files can be used by OpenText support to find the root cause of an application crash

Does anyone have any experience here?

Any other ideas to find the cause of non-reproducible crashs? WinDbg?
Best regards,
Uwe van der Horst
Advo-web GmbH

User avatar
markus.essmayr
Site Admin
Site Admin
Austria
Posts: 1024
Joined: 06 Mar 2017, 06:07
Location: Austria

Re: Handling of application crashes

Post by markus.essmayr » 25 May 2020, 18:47

Hi,

I used WinDbg in the past which is a really powerful tool!
Of course, it's UI needs getting used to and may put off a lot of people when they use it the first time.
But it's definitely worth to have a look at it and it is able to open minidump files!
So before you send those files to OpenText, try to load them into WinDbg and see if you can get useful information out of it.

Max
Markus Eßmayr
teamdeveloper@t-mx.com

Uwe van der Horst
Site Admin
Site Admin
Germany
Posts: 479
Joined: 05 Mar 2017, 14:21
Location: Wetter (Ruhr), Germany

Re: Handling of application crashes

Post by Uwe van der Horst » 31 May 2020, 17:38

Hi Max,

thank you. WinDbg is certainly a powerful tool, but it takes a lot of time to work yourself in. I see that it is part of the Windows Software Development Kit (SDK). Full download of the SDK is > 1 GB. Therefore I tried the Debug Diagnostic Tool (DebugDiag). It is smart and self-explanatory. Just load the minidump and you get a report where you see memory leaks, detailed information about the loaded dlls and the faulting thread. Really great!
Best regards,
Uwe van der Horst
Advo-web GmbH

KimF
Finland
Posts: 69
Joined: 04 May 2017, 03:49
Location: Finland

Re: Handling of application crashes

Post by KimF » 01 Jun 2020, 10:50

We have been fighting with memory leaks together with OpenText and Micsto for quite a while...
These problems made application to creash randomly
These problems appeared after MS server/workstation was updated to 2012/8.1

Windbg is a quite good tools to scan for these leaks

For us GetVersionExW( ) seems to have created biggest problems
We also found some memory problems in M!Tbl's older versions

Kim

Return to “General Discussion”

Who is online

Users browsing this forum: No registered users and 0 guests