This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA/PATCH] breakpoint.c: fix until command

Elena Zannoni wrote:
> Daniel Jacobowitz writes:
>  > On Fri, Jan 03, 2003 at 01:52:07PM -0800, Michael Snyder wrote:
>  > > > I'm still undecided about what to do if LOCATION is not in the
>  > > > function.  Maybe you're right and we should make this an error.  What
>  > > > if LOCATION is in the frame that called this one?
>  > >
>  > > My thoughts have run in similar grooves.  ;-)
>  > > The sticking point is "is <location> in the current function?"
>  > > I believe we can answer that, by calling find_pc_partial_function.
>  > > That will give us the function's address range, and we can then
>  > > immediately determine whether <location> is in (use frame-relative bp),
>  > > or out (don't do that).
>  >
>  > I think we're making actual progress here.... I agree.
>  >
> <rant>
> but this is the opposite of what we agreed on a month ago.
> </rant>
> We are giving up on the until foo behavior now.

I thought we were trying to find a way to accomodate both behaviors.

> Anyway, do an 'help until' in gdb.... the text of it goes back as
> far as the frame checking code, which just shows that this whole thing
> was botched from day one.

Yep, the frame behavior has never been documented.

Maybe we should really find out whether anyone else's recollections
about this match mine...

[Yo Stan...]

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]