Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| [7 earlier articles] |
| Re: Debugging of optimized code danhicks@aol.com (1995-01-26) |
| Re: Debugging of optimized code baynes@ukpsshp1.serigate.philips.nl (1995-01-26) |
| Re: Debugging of optimized code sam@ccnet.com (1995-01-27) |
| 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) |
| 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) |
| [8 later articles] |
| Newsgroups: | comp.compilers |
| From: | miker@metaware.com (Mike Ross) |
| Keywords: | optimize, debug |
| Organization: | Compilers Central |
| References: | 95-01-036 95-01-054 |
| Date: | Tue, 24 Jan 1995 12:46:58 GMT |
The old Apollo DOMAIN compilers and DDE debugger were
quite capable of debugging optimized code. The object
format was COFF, but a separate DEBUG section held
the debugger information in a proprietary format.
This worked even in after procedure inlining. The times
that the user could notice things were different than
in unoptimized code were when encountering code where
cross jumping had been applied, and when attempting
to examine a variable that was no longer live.
Mike
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.