Skip to content

Recreate Callstack Feature #64

@Aragas

Description

@Aragas

Starting from version 4, Crash Reports have the full stacktrace + IL Offsets.
Because we have the ability to get the game's .dll files from Steam and create .pdb files on the fly if needed, we should be able to show the user both the faulty methods and the lines responsible for the fault.

There are some caveats:

  • A game update could break the feature and show an incorrect line. The Crash Report doesn't store the ChangeSet used. We'll need to store the changeset to be sure that the binary is correct for the crash report. If they differ, a warning prompt should be enough.
  • We'll need to either rate limit the feature or cache the game binaries, with invalidation on a game update that we'll need to detect in a way that will only invalidate the updated branch, not all of them
  • Expose the necessary info in CrashReportParser
  • Create a caching layer for the game binaries
  • Extract the source code from methods
  • Apply the IL Offset to the source code
  • Create a page for displaying the source code with the highlighted line

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions