Talk:Stack trace

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Mid	This article has been rated as Mid-importance on the project's importance scale.
	This article is supported by WikiProject Software (assessed as Mid-importance).

I really do not know how to make this fit into this article, however I think it's very useful for others:

http://www-128.ibm.com/developerworks/library/l-cppexcep.html?ca=dnt-68 is a nice article about how to utilize backtrace() and backtrace_symbols() for stacktraces in C++ Exception handling.

-Tino 91.64.74.131 16:46, 19 September 2007 (UTC)[reply]

Other contexts?[edit]

Can "stack trace" or "traceback"/"backtrace" be used in other contexts besides just displaying the active stacks? For instance, can it be applied to the act of debugging an application using tracepoints to trace a bug to its source up the call stack?--Subversive Sound (talk) 12:21, 6 June 2010 (UTC)[reply]

I would like to see more about the history behind when these were implemented in different computing systems. I see a strong parallel to telephone switching, but can't find any sources. See this video about the No 5 Crossbar on YouTube (XKyXCZV_faY) at 9:31 about what is basically a stack trace for a mechanical computer. Rkedge (talk) 15:15, 5 June 2020 (UTC)[reply]

try..catch[edit]

There should be something about try..catch and about exceptions I think. Exceptions in javascript hold stack property that hold stack trace of an exception, from last function to place where exception was thrown. jcubic (talk) 16:10, 18 May 2014 (UTC)[reply]

Done Added Exception handling to See also. NE Ent 14:29, 5 October 2017 (UTC)[reply]

Dubious: "continuously allocated"[edit]

From the intro, this doesn't make a lot of sense: "Memory is continuously allocated on a stack but not on a heap, thus reflective of their names." Shouldn't that be "continually" (in repeated succession), not "continuously" (without interruption)?

In any case, I don't see how it is reflective of their names in any other than a tautological sense. BMJ-pdx (talk) 15:58, 19 March 2024 (UTC)[reply]