[Q] How to diagnose crash?

[jheliker]

Hello @lelegard

I'm trying to determine how to diagnose a crash, I've been running some tests with tsp.exe on Windows and occasionally have caused a crash that does not output anything on STDERR or STDOUT, however, I can see in Event Viewer that tsp.exe is crashing.

How can I diagnose this further?

AppName tsp.exe
AppVersion 3.37.3670.0
AppTimeStamp 65f95f5b
ModuleName unknown
ModuleVersion 0.0.0.0
ModuleTimeStamp 00000000
ExceptionCode c0000005
FaultingOffset 0000000000000244
ProcessId 0x13ea0

Thank you!

[lelegard]

Hi @jheliker

Hard to say. Your exception code in a memory access violation, so it may be any corrupted pointer in any library, anywhere in the process address space. If it happens randomly only, after hours of execution, then it is close to impossible to characterize. Additionally, you use Windows, a system in which troubleshooting is notoriously harder than on Linux.

I would suggest several things.

• Provide the exact configuration and version of Windows and TSDuck.
• Provide the complete tsp command line.
• Run tsp with option --monitor and carefully keep the output/error file to tsp. This option tracks CPU and memory usage inside the process. Access violation may appear in case of memory leak when the address space is saturated and memory allocation fails. Note, however, that TSDuck was regularly tested with valgrind on Linux and zero memory leak was found.

Recently, a TSDuck user did fuzzing tests and found a few issues with corrupted video data streams. They were all fixed before version 3.37. He also did sanity tests with ASAN and UBSAN. All potential issues were also fixed before 3.37.