본문으로 바로 가기
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. 오전 6:05에 게시됨 · 카탈로그 리비전 5bc079fe355af2214bc0

앱에 내장된 스냅샷을 표시하고 있습니다(콘텐츠 소스가 설정되지 않았습니다). 소스에는 더 새로운 콘텐츠가 있을 수 있습니다.