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
However, we have the necessary information to symbolicate callstacks for mods that provide PDBs which we can use in Callstack::print_probable_callstack
This makes investigating crash logs much easier, particularly when provided by users who do not have additional debug tools at their disposal.
Is there a technical limitation that prevented this from being included in CrashLogger prior (aside from it only being usable for some callstack frames), or are PRs welcome?
The text was updated successfully, but these errors were encountered:
CrashLogger only symbolicates the thrown exception -- not the callstack that led to the exception. Example:
However, we have the necessary information to symbolicate callstacks for mods that provide PDBs which we can use in
Callstack::print_probable_callstack
Result with local changes:
This makes investigating crash logs much easier, particularly when provided by users who do not have additional debug tools at their disposal.
Is there a technical limitation that prevented this from being included in CrashLogger prior (aside from it only being usable for some callstack frames), or are PRs welcome?
The text was updated successfully, but these errors were encountered: