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.
इस कैटलॉग के बारे में
साथ में शामिल स्नैपशॉट · 15 नव॰ 2026, 6:05 am पर प्रकाशित · कैटलॉग रिविज़न 5bc079fe355af2214bc0
ऐप के साथ आया स्नैपशॉट दिखाया जा रहा है (कोई कंटेंट स्रोत कॉन्फ़िगर नहीं है)। स्रोत पर नया कंटेंट हो सकता है।