Skip to lesson
Exit
Debugging & Troubleshooting Method1 / 2

1 min lesson

Read a stack trace from both ends

Walk through "Read a stack trace from both ends" in order, then name the proof that tells you it worked.

Step 1 of 2

Read a stack trace from both endsfind the first line that's yours

Read top-down to see the frame that actually threw and bottom-up to see what triggered the chain. The line that matters is usually the first one that isn't framework or node_modules code - that's where your system meets the failure.

  1. 1Find the throwing frame. The top of the trace names the error and where it was raised.
  2. 2Walk down to the first non-framework line. Skip node_modules and runtime internals until you hit Cursor or extension code.
  3. 3Read the message literally. ENOTFOUND, EACCES and 429 each point at a different layer - DNS, permissions, rate limiting.
  4. 4Tie it to a timestamp. Match the trace time against the user's report and any server-side signal.