Re: [RFC] breakpoints and function prologues...

[Michael Snyder <msnyder at redhat dot com>]

Andrew Cagney wrote:
> 
> > Andrew Cagney wrote:
> >
> >>
> >
> >> >
> >> > Most users I have talked to think that setting a break on the "{" at the beginning of a function means the same thing as setting a breakpoint on the function.  But that is not the case.   "break funcName" is AFTER the prologue, "break file:<line containing "{"> is the true function beginning.
> >
> >>
> >> Don't forget that ``break func'' is is going to change.  It's going to
> >> go back to the start of the function!
> >
> >
> > ???
> > Since when?
> 
> When an architecture enables CFI.  CFI removes any technical reason for
> skipping the prologue (what break foo does'') -- CFI allows you to find
> the value of registers and variables at any point in the code.
> 
> Of course,we could always leave ``break foo''.

You mean leave SKIP_PROLOGUE on ``break foo'', right?
Frankly, I see no reason to change it.