11/01/1990 09:00 AM
Computer Science
Optimizing compilers produce code that impedes debugging. An important facility for an interactive debugger of optimized programs is to be able to provide a call-stack trace, listing active subroutines in reverse order of their invocations. This facility relies on information provided by code within each called routine. This paper describes an alternative way to support this facility in the circumstance that this code is optimized away.
