Re: Debugging of optimized code

danhicks@aol.com (DanHicks)
Sun, 29 Jan 1995 22:12:18 GMT

          From comp.compilers

Related articles
[10 earlier articles]
Debugging of optimized code ssimmons@convex.convex.com (1995-01-27)
Re: Debugging of optimized code monnier@di.epfl.ch (Stefan Monnier) (1995-01-27)
Re: Debugging of optimized code urs@engineering.ucsb.edu (1995-01-27)
Re: Debugging of optimized code miker@metaware.com (1995-01-24)
Re: Debugging of optimized code cef@geodesic.com (Charles Fiterman) (1995-01-25)
Re: Debugging of optimized code danhicks@aol.com (1995-01-27)
Re: Debugging of optimized code danhicks@aol.com (1995-01-29)
AS/400 (was: Debugging of optimized code) SAND_DUANE@tandem.com (1995-01-31)
Re: Debugging of optimized code monnier@di.epfl.ch (Stefan Monnier) (1995-01-27)
Re: Debugging of optimized code jqb@netcom.com (1995-02-02)
Debugging of optimized code ssimmons@convex.convex.com (1995-02-02)
Re: Debugging of optimized code copperma@grenoble.rxrc.xerox.com (1995-01-30)
Re: Debugging of optimized code wicklund@Intellistor.COM (1995-01-30)
[8 later articles]
| List of all articles for this month |
Newsgroups: comp.compilers
From: danhicks@aol.com (DanHicks)
Keywords: debug, optimize
Organization: America Online, Inc. (1-800-827-6364)
References: 95-01-077
Date: Sun, 29 Jan 1995 22:12:18 GMT

> The cost of always providing a frame pointer is small so it
> is reasonable to always do it.


Actually, competitive pressures make even this small cost unacceptable in
some cases (especially leaf procedures). However, it is possible (if one
is sufficiently determined and can get the compiler and debugger folks to
work together) to associate a table with the code ("code header" or
"traceback table") which gives the debugger the necessary clues for
unraveling the stack.


Dan Hicks
--


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.