http://tech.saigonist.com/taxonomy/term/106/all en http://tech.saigonist.com/b/code/stack-traces-backtraces-call-stacks-explained-javascript-python-php <span class="submitted-by">March 12, 2016</span><div class="field_tags"><span class="label label-info"><a href="/tags/stack">stack</a></span> <span class="label label-info"><a href="/tags/call-stack">call stack</a></span> <span class="label label-info"><a href="/tags/stack-trace">stack trace</a></span> <span class="label label-info"><a href="/tags/javascript">javascript</a></span> <span class="label label-info"><a href="/tags/php">php</a></span> <span class="label label-info"><a href="/tags/python">python</a></span> <span class="label label-info"><a href="/tags/bash">bash</a></span> </div><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p>People are rarely happy to see a stack trace. A stack trace often appears when software encounters an exception, an unexpected error which can't be handled gracefully and therefore most stop execution of the program. What the stack trace shows is what was happening in the moments leading up to the bug. The stack is called a stack because each item (each function call) is stacked on top of the previous one in a special part of computer memory called the stack. Most computers and programming languages work with a stack. In programs written in programming languages without side effects, a...</p></div></div></div> Fri, 11 Mar 2016 19:37:27 +0000 tomo 64 at http://tech.saigonist.com