From mboxrd@z Thu Jan  1 00:00:00 1970
From: Joern Rennecke <amylaar@cambridge.redhat.com>
To: dan@cgsoftware.com (Daniel Berlin)
Cc: mark@codesourcery.com (Mark Mitchell), wilson@cygnus.com, gcc@gcc.gnu.org
Subject: debugging optimized programs (Was: Re: Bootstrap failure of gcc-ss-20010409 in ia64)
Date: Wed, 18 Apr 2001 14:35:00 -0000
Message-id: <200104182134.f3ILYxs07012@phal.cambridge.redhat.com>
References: <m21yqrung8.fsf@dynamic-addr-83-177.resnet.rochester.edu>
X-SW-Source: 2001-04/msg00894.html

> I've used debuggers and compilers that support optimized debugging,
> using dwarf2, to a point that except for variables that were optimized
> out, i couldn't tell the difference between the optimized version, and
> the non-optimized one, for debugging.

So what does the debugger do when you ask it to step one source level line
forward (gdb 'n' command) when code from different lines is heavily
intermingled by scheduling?