Explain a stack trace
A long error message translated: what happened, where in your own code, and what to check first.
- Type
- Prompt
- Level
- Beginner
- Time
- about 3 min
Results depend on the tool, the model and what you enter.
Fill in
What you type stays in this browser window. We store and send nothing.
- Python 3.12 with Django
- Node.js 22 with Express
- Java 21 with Spring Boot
- PHP 8.3 with Laravel
- Kotlin for Android
- beginner, first app of my own
- one or two years of experience
- experienced, but new to this framework
- coming from another language
- expert, keep it short
Your prompt
Explain this stack trace from a project using [Language/framework]. My level: [Level]. 1. What happened, in one sentence? 2. Which lines belong to my code and which to libraries? 3. The three most likely causes, ranked. 4. What do I check first, with a concrete command or log output? Do not guess about code you cannot see; ask if something is missing. Stack trace: [Stack trace]
Matching tools
Tools from our catalog that this prompt works well with.
- ChatGPT Prices and limits
- Claude Prices and limits
- Cursor Prices and limits
How to use it
- Fill in the fields or tap a suggestion. Leave out names, addresses and other personal data.
- Copy the finished prompt into a tool of your choice.
- Run the suggested first check and report the result back instead of applying a fix straight away.
Works in these tools
Prompts work in many chat and generator tools. This selection comes from our catalog; prices as shown on the tool page.
- ChatGPT Free planfrom 8 USD per month
- Claude Free plan
- Cursor Free planfrom 8 USD per month
- GitHub Copilot Free planfrom $10
Why does this work?
Separating your code from library code shows you where to look. The rule to ask instead of guess prevents invented causes.
Tips
- If you find them, also send the two lines of code around the reported location.