Skip to content

Compare two builds to triage a crash

Use a known-good and failing build of your application to isolate what changed around a reproducible crash and hand the evidence to a maintainer.

Tool
REA
Provider or project
JoasASantos community collection
Source type
Community-authored

Who should use it

Release engineers and maintainers who control both builds and have a reproducible failure.

Practical uses

  • Triage a crash that appears after a packaging change.
  • Turn a crash report into a concise handoff with testable hypotheses.

How to use it

  1. Record each build identifier and collect a sanitized stack trace from the same test input.
  2. Compare the top failing frames and the configuration or dependency versions for those modules.
  3. Request one likely cause and a minimal experiment to confirm it.

Original example

Our sample viewer opens the same local fixture in build A but crashes in build B. Compare the provided stack traces and dependency lists. Identify one changed code path to verify in a unit test.

Limitations

An optimized or stripped build may omit symbols. Correlation across builds is evidence for a hypothesis, which still needs a reproducer.

Sources and versions

The explanation and example were written for this directory. The cited files record the source version.

Related prompts

Browse more prompts

Search directory

Try a search