fix(Core/Debugging): Improve SymInitialize fail message (#15424)

* 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-pick commit (6e37438e5d)

Co-authored-by: ihm-tswow <76849026+ihm-tswow@users.noreply.github.com>
This commit is contained in:
Kitzunu
2023-03-17 07:19:03 +01:00
committed by GitHub
parent 08e1a822f5
commit b32d3506de

View File

@@ -674,8 +674,13 @@ void WheatyExceptionReport::GenerateExceptionReport(
// Initialize DbgHelp
if (!SymInitialize(GetCurrentProcess(), 0, 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"));
}
CONTEXT trashableContext = *pCtx;