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

Jim Ingham
2002-08-24T21:05:27Z

Yes, we could change -break-insert to do this.

It would still break when somebody uses the console to set breakpoints
from within Project Builder, however. Like with Insight, we try to
support the console as well as we can from PB (we don't do as good a
job as Insight, but we are working towards it).

I guess we could go note the breakpoint set event, delete the
breakpoint that was just set IF it was set with file:line, and reset it
with the "move me past the prologue" cookie. But this seems a bit of a
hack.

The other option is to add a "set make-old-gdb-users-unhappy-with-break
{on,off}" command, and set that from the IDE when we start up gdb. I'm
not real thrilled about this either...

Jim

On Friday, August 23, 2002, at 11:31 AM, Andrew Cagney wrote:

>> On Thursday, August 22, 2002, at 04:34 PM,
>> gdb-patches-digest-help@sources.redhat.com wrote:
>>> The question is, is there a strong reason to change a behavior
>>> that has been consistent for a very long time (even if undocumented).
>>> Even if the ability to debug the prologue is un-important for most
>>> users, it is important to some, and those users (GCC developers,
>>> for instance) may be quite accustomed to the current behavior.
>>> I am, for instance...
>
>> The varobj code will fail with file:line number breakpoint setting on
>> the { that starts the function. This is, of course, not a problem
>> for command-line gdb users, but varobj IS a part of gdb... Until we
>> have the CFI stuff well enough set up that, on landing at the
>> beginning of the prologue, the scanner will tell us where the stack
>> frame WILL be when it has been set up so we can record this properly,
>> this will be a problem.
>
> Aren't varobj/MI and the CLI separate? varobj/MI could easily request
> a prologue adjusted breakpoint without modifying the CLI.
>
> enjoy,
> Andrew
>
>
>
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Jim Ingham
jingham@apple.com
Developer Tools - gdb