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日 清晨6:05 · 目錄修訂版 5bc079fe355af2214bc0
正在顯示應用程式內建的快照(尚未設定內容來源)。來源處可能已有更新的內容。