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
In #84 a stack trace was shown which included symbols that didn't make sense. I've had another user mention to me odd symbols in trace output on windows. I have been unable to reproduce such issues, verify the behavior, or investigate whether the problem lies in dbghelp or cpptrace.
I suspect, however, that if there is a problem it may be with how modules are handled in the dbghelp code.
I'll need more information to confirm this issue and resolve it.
The text was updated successfully, but these errors were encountered:
It looks like in the other user's case the issue was a leftover PDB from a debug build that became bogus for their release build. So, back to only one case. I will look into a way to check signatures between the pdb and exe, however, to prevent this.
In #84 a stack trace was shown which included symbols that didn't make sense. I've had another user mention to me odd symbols in trace output on windows. I have been unable to reproduce such issues, verify the behavior, or investigate whether the problem lies in dbghelp or cpptrace.
I suspect, however, that if there is a problem it may be with how modules are handled in the dbghelp code.
I'll need more information to confirm this issue and resolve it.
The text was updated successfully, but these errors were encountered: