You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 5, 2023. It is now read-only.
agent_logger.exe is failing to symbolize the stack traces.
The symbolization is done in the AgentLogger::AppendTrace, this function do the following things:
It initialize the symbol handler via SymInitialize, this is working fine (or it at least return true)
It append the path of the PDB of the running process to the symbol search path. This is working fine (we successfully augment the symbol search path with the path containing the PDBs that we need).
It calls SymFromAddr for each line of this stack trace, this is currently failing, GetLastError returns the code 126 ("The specified module could not be found").
There's several possible culprits:
The version of dbghelp that we're using isn't the right one.
msdiaXXX.dll isn't registered (but it'll probably fail in the SymInitialize function if it was the case ?)
We're doing something silly in the AppendTrace function and we've been lucky, until today.
I suspect that it has started to fail with the switch to VS2015, or to the Win10 SDK.
The text was updated successfully, but these errors were encountered:
agent_logger.exe is failing to symbolize the stack traces.
The symbolization is done in the AgentLogger::AppendTrace, this function do the following things:
There's several possible culprits:
I suspect that it has started to fail with the switch to VS2015, or to the Win10 SDK.
The text was updated successfully, but these errors were encountered: