跳转到主要内容
kitlocal.dev

Diagnose a stack trace

Turns a stack trace plus a short description of what you were doing into ranked hypotheses, the first checks to run for each, and what extra evidence would settle it.

此资源仅提供英文版本。

提示词是你复制到自己助手中的文本。KitLocal 不会运行它们。

填写变量

你输入的内容只保留在此浏览器中,不会添加到 URL、保存或发送到任何地方。

预览

仍需填写:Stack trace, What were you doing / what changed

Help me diagnose this error. Runtime: . Reproducible: Unknown.

What I was doing / what changed:
{{situation}}

Stack trace:
```
{{stackTrace}}
```

Respond with:
1. A one-sentence reading of what the exception says (not a guess about the cause).
2. Up to four hypotheses ranked by likelihood. For each: why the trace supports it, and the
   single quickest check that would confirm or rule it out.
3. The extra evidence you would ask for (logs, versions, inputs) if none of the checks settle it.
4. Only then, a suggested fix for the most likely hypothesis.
Mark anything you are unsure about as "unverified". Do not claim a root cause you cannot see.

用途

Move from a wall of stack frames to a short list of testable hypotheses.

适用场景

  • An exception appears and the cause is not obvious from the top frame.
  • You want a disciplined checklist instead of guessing.

需要准备的内容

  • The full stack trace, including "Caused by" sections.
  • What you were doing, what changed recently, and whether it is reproducible.

预期输出

A numbered Markdown answer following the four sections above.

关于此目录

内置快照 · 发布于 2026年11月15日 06:05 · 目录修订版 5bc079fe355af2214bc0

正在显示应用内置的快照(未配置内容来源)。来源处可能已有更新的内容。