Read an Error Decoder report
Start with the diagnosis, compare it with the log and follow the verification steps.
Start here
- Include the error and nearby log lines.
- Choose the tool and language if detection needs correcting.
What you get
- Relevant evidence, a possible cause and suggested changes.
- Checks to run after editing your project.
Read the result
- Diagnosis summarises the recognised error pattern.
- Evidence quotes the log lines used for the explanation.
- Fixes describe what to inspect or change; verification tells you what to run next.
When more context is needed
- A confidence value describes the match to diagnostic rules, not the probability that a fix will work.
- An unrecognised error needs more context. Include the command, tool version and relevant source references.
- No diagnostics found means the supplied text did not contain a recognised error or warning.
Save and export
- Signed-in reports appear in History. Export a result as Markdown or JSON.
- Saved reports may include excerpts even when raw-log storage is disabled.
- Confirm changes with your own simulation or synthesis run.