This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA/PATCH] breakpoint.c: fix until command
- From: Michael Snyder <msnyder at redhat dot com>
- To: Michael Elizabeth Chastain <mec at shout dot net>
- Cc: ezannoni at redhat dot com, drow at mvista dot com, gdb-patches at sources dot redhat dot com
- Date: Fri, 03 Jan 2003 15:33:31 -0800
- Subject: Re: [RFA/PATCH] breakpoint.c: fix until command
- Organization: Red Hat, Inc.
- References: <200301031648.h03GmHa15365@duracef.shout.net>
Michael Elizabeth Chastain wrote:
>
> Hi Elena,
>
> > See the thread from November on gdb@sources.
>
> Gotcha. Thanks.
>
> > I think that using decode_line_1 may be the real problem, because that
> > allows all kind of arguments to be used, just like for a breakpoint.
>
> I think the real problems are: (a) we haven't designed what should
> actually happen in all cases, and then (b) Daniel J says that some
> decision-making information is not reliable to get (when the user says
> 'until 70' gdb cannot reliably tell whether line 70 is in the current
> function).
Yes it can, unles code motion actually breaks functions into multiple
chunks. find_pc_partial_function will return the function's bounding
addresses.