Re: gdb not breaking on break statements
Re: gdb not breaking on break statements
- Subject: Re: gdb not breaking on break statements
- From: Jeffrey Oleander <email@hidden>
- Date: Sat, 10 Nov 2007 17:06:42 -0800 (PST)
> Fritz Anderson <email@hidden> wrote:
>> On 2007-11-08 at 19:28, Steve Checkoway wrote:
>>> On 2007-11-08 at 16:44, Jason Molenda wrote:
>>> As far as the debugger knows, line 7 is a blank line
>>> or a comment or something like that. Even though
>>> this is compiled without optimization, the way that
>>> the compiler generates assembly for this source
>>> code is not exactly what you might have expected.
What it boils down to is that it may not be "optimized" but
it has been optimized a little.
I ye ancient days, we would choose from a number of levels
of optimization (rather than menus of specific kinds of
optimizations that came later). If you choose "debug" it
would have generated the expected code with a no-op if
necessary to generate an additional address for the
programmer to stop there if he got the desire to do so.
Now, certain optimizations are made even at the lowest
level selectable by the software developer.
But, what if the user does something to inhibit that
optimization at a crucial point like this, like making it
seem that a variable that was going to be used later was
affected there, and/or even explicitly putting a statement
label there? Of course, you'd have to surround it with #IF
DEBUG or whatever, and you'd never really be sure whether
the optimized version of the code was doing the desired
thing because, like the electron, when we try to bounce
some energy off of it to figure out what it's doing or
where it is, we've changed what it's doing and where it is.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden