[Interest] Crash in Qt OpenSSL thread

2021-03-21 Thread Alexander Dyagilev
Hello, One of our users reported the following crash: Unhandled exception at 0x7FF82C50EF89 (ntdll.dll) in fdm.exe.3964.dmp: 0xC374: A heap has been corrupted (parameters: 0x7FF82C5777F0). With the following stack trace: ntdll.dll!RtlReportFatalFailure()    Unknown ntdll.dll!Rt

Re: [Interest] Crash in Qt OpenSSL thread

2021-03-23 Thread Mårten Nordheim
From: Interest on behalf of Alexander Dyagilev Sent: Sunday, March 21, 2021 20:32 To: Interests Qt Subject: [Interest] Crash in Qt OpenSSL thread Hello, One of our users reported the following crash: Unhandled exception at 0x7FF82C50EF89 (ntdll.dll) in fdm.exe.3964.dmp: 0xC374: A heap has

Re: [Interest] Crash in Qt OpenSSL thread

2021-03-23 Thread Roland Hughes
I am assuming that running the application under Valgrind at the client site to catch the crash is not an option. Suggestions in order of least amount of pain. Since I see .dll in your output I will also assume Windows platform. 1.) Run CppCheck and other static source analysis tools to make