From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13545 invoked by alias); 3 Jan 2003 23:33:59 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 13538 invoked from network); 3 Jan 2003 23:33:58 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by 209.249.29.67 with SMTP; 3 Jan 2003 23:33:58 -0000 Received: from int-mx2.corp.redhat.com (nat-pool-rdu-dmz.redhat.com [172.16.52.200]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h03N6NB31388 for ; Fri, 3 Jan 2003 18:06:24 -0500 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx2.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h03NXXn27402; Fri, 3 Jan 2003 18:33:39 -0500 Received: from redhat.com (reddwarf.sfbay.redhat.com [172.16.24.50]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id h03NXVn31066; Fri, 3 Jan 2003 15:33:31 -0800 Message-ID: <3E161DCB.8B3DF213@redhat.com> Date: Fri, 03 Jan 2003 23:33:00 -0000 From: Michael Snyder Organization: Red Hat, Inc. X-Accept-Language: en MIME-Version: 1.0 To: Michael Elizabeth Chastain CC: ezannoni@redhat.com, drow@mvista.com, gdb-patches@sources.redhat.com Subject: Re: [RFA/PATCH] breakpoint.c: fix until command References: <200301031648.h03GmHa15365@duracef.shout.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2003-01/txt/msg00122.txt.bz2 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.