[{"data":1,"prerenderedAt":139},["ShallowReactive",2],{"term-s\u002Fstack-trace":3,"related-s\u002Fstack-trace":122},{"id":4,"title":5,"acronym":6,"body":7,"category":103,"description":104,"difficulty":105,"extension":106,"letter":107,"meta":108,"navigation":78,"path":109,"related":110,"seo":116,"sitemap":117,"stem":120,"subcategory":6,"__hash__":121},"terms\u002Fterms\u002Fs\u002Fstack-trace.md","Stack Trace",null,{"type":8,"value":9,"toc":97},"minimark",[10,15,19,23,26,30,86,90,93],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 — The Vibe Check",[16,17,18],"p",{},"A stack trace is the error report that tells you exactly which functions were called right before your code crashed. It is like a trail of breadcrumbs from where you are back to where everything started going wrong. The most important line is usually near the top.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"A stack trace is a sequential report of the function call stack at the moment an exception or error occurs. Each entry shows the function name, file path, and line number. Reading a stack trace bottom-up shows the call chain from the program entry point; top-down shows the closest point to the failure. Stack traces are the primary starting point for debugging runtime errors.",[11,27,29],{"id":28},"show-me-the-code","Show Me The Code",[31,32,37],"pre",{"className":33,"code":34,"language":35,"meta":36,"style":36},"language-javascript shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","\u002F\u002F Example JS stack trace:\n\u002F\u002F TypeError: Cannot read properties of null (reading 'name')\n\u002F\u002F   at getUserName (users.js:42:17)    \u003C-- where it crashed\n\u002F\u002F   at renderProfile (profile.js:18:5)  \u003C-- called by this\n\u002F\u002F   at App.render (App.js:95:3)         \u003C-- called by this\n\n\u002F\u002F Start debugging at line 42 of users.js\n","javascript","",[38,39,40,49,55,61,67,73,80],"code",{"__ignoreMap":36},[41,42,45],"span",{"class":43,"line":44},"line",1,[41,46,48],{"class":47},"sHwdD","\u002F\u002F Example JS stack trace:\n",[41,50,52],{"class":43,"line":51},2,[41,53,54],{"class":47},"\u002F\u002F TypeError: Cannot read properties of null (reading 'name')\n",[41,56,58],{"class":43,"line":57},3,[41,59,60],{"class":47},"\u002F\u002F   at getUserName (users.js:42:17)    \u003C-- where it crashed\n",[41,62,64],{"class":43,"line":63},4,[41,65,66],{"class":47},"\u002F\u002F   at renderProfile (profile.js:18:5)  \u003C-- called by this\n",[41,68,70],{"class":43,"line":69},5,[41,71,72],{"class":47},"\u002F\u002F   at App.render (App.js:95:3)         \u003C-- called by this\n",[41,74,76],{"class":43,"line":75},6,[41,77,79],{"emptyLinePlaceholder":78},true,"\n",[41,81,83],{"class":43,"line":82},7,[41,84,85],{"class":47},"\u002F\u002F Start debugging at line 42 of users.js\n",[11,87,89],{"id":88},"when-youll-hear-this","When You'll Hear This",[16,91,92],{},"\"Post the stack trace so I can see where it crashed.\" \u002F \"The stack trace points to line 42 — that's where the null is.\"",[94,95,96],"style",{},"html pre.shiki code .sHwdD, html code.shiki .sHwdD{--shiki-light:#90A4AE;--shiki-light-font-style:italic;--shiki-default:#546E7A;--shiki-default-font-style:italic;--shiki-dark:#676E95;--shiki-dark-font-style:italic}html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":36,"searchDepth":51,"depth":51,"links":98},[99,100,101,102],{"id":13,"depth":51,"text":14},{"id":21,"depth":51,"text":22},{"id":28,"depth":51,"text":29},{"id":88,"depth":51,"text":89},"general","A stack trace is the error report that tells you exactly which functions were called right before your code crashed.","beginner","md","s",{},"\u002Fterms\u002Fs\u002Fstack-trace",[111,112,113,114,115],"Debug","Error","Exception","Debugger","Logging",{"title":5,"description":104},{"changefreq":118,"priority":119},"weekly",0.7,"terms\u002Fs\u002Fstack-trace","dkvUkVmCWZK0UGQwtlQJbwHWI4180-vStjPe1Fl3Qjo",[123,126,130,133,136],{"title":111,"path":124,"acronym":6,"category":103,"difficulty":105,"description":125},"\u002Fterms\u002Fd\u002Fdebug","Debugging is the process of finding and fixing the gremlins in your code. Something is broken, and you need to play detective — adding clues (console.",{"title":114,"path":127,"acronym":6,"category":103,"difficulty":128,"description":129},"\u002Fterms\u002Fd\u002Fdebugger","intermediate","A debugger is a special tool that lets you pause your running program mid-execution, look around at all the variables, and step through the code one line a...",{"title":112,"path":131,"acronym":6,"category":103,"difficulty":105,"description":132},"\u002Fterms\u002Fe\u002Ferror","An error is when your program says 'I cannot do that' and either stops or complains loudly. It is the computer's way of telling you something went wrong.",{"title":113,"path":134,"acronym":6,"category":103,"difficulty":128,"description":135},"\u002Fterms\u002Fe\u002Fexception","An exception is a special kind of error that 'throws' itself up through your code like a hot potato, looking for someone to catch it.",{"title":115,"path":137,"acronym":6,"category":103,"difficulty":105,"description":138},"\u002Fterms\u002Fl\u002Flogging","Logging is writing a diary for your program.",1776518314869]