Mirror/TrinityCore
1
0
Fork 0
mirror of https://github.com/TrinityCore/TrinityCore.git synced 2026-01-15 23:20:36 +01:00
Code Issues Packages Projects Releases Wiki Activity

Core/Debugging: Improve SymInitialize fail message (#28206)

Browse Source 
* clarify that this is not the crash error, but an error with the crash report itself
* improve formatting and message boundaries
* warn the reader that this means the call stack symbols may be inaccurate

(cherry picked from commit 6e37438e5d)
This commit is contained in:
ihm-tswow
2022-08-19 11:14:07 +02:00
committed by Shauren
parent 8684af145d
commit cec4cb0222
1 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
src/common/Debugging/WheatyExceptionReport.cpp
View File

@@ -722,8 +722,13 @@ PEXCEPTION_POINTERS pExceptionInfo)
// Initialize DbgHelp
if (!SymInitialize(GetCurrentProcess(), nullptr, TRUE))
{
Log(_T("\n\rCRITICAL ERROR.\n\r Couldn't initialize the symbol handler for process.\n\rError [%s].\n\r\n\r"),
ErrorMessage(GetLastError()));
Log(_T("\r\n"));
Log(_T("----\r\n"));
Log(_T("SYMBOL HANDLER ERROR (THIS IS NOT THE CRASH ERROR)\r\n\r\n"));
Log(_T("Couldn't initialize symbol handler for process when generating crash report\r\n"));
Log(_T("Error: %s\r\n"), ErrorMessage(GetLastError()));
Log(_T("THE BELOW CALL STACKS MIGHT HAVE MISSING OR INACCURATE FILE/FUNCTION NAMES\r\n\r\n"));
Log(_T("----\r\n"));
}
if (pExceptionRecord->ExceptionCode == 0xE06D7363 && pExceptionRecord->NumberParameters >= 2)