From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24126 invoked by alias); 11 Feb 2004 06:19:10 -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 24118 invoked from network); 11 Feb 2004 06:19:09 -0000 Received: from unknown (HELO monty-python.gnu.org) (199.232.76.173) by sources.redhat.com with SMTP; 11 Feb 2004 06:19:09 -0000 Received: from [207.232.27.5] (helo=WST0054) by monty-python.gnu.org with asmtp (Exim 4.24) id 1Aqnhp-0003QA-Ge; Wed, 11 Feb 2004 01:18:41 -0500 Date: Wed, 11 Feb 2004 06:19:00 -0000 Message-Id: From: Eli Zaretskii To: Jeff Johnston CC: gdb-patches@sources.redhat.com In-reply-to: <402974E1.8090909@redhat.com> (message from Jeff Johnston on Tue, 10 Feb 2004 19:18:41 -0500) Subject: Re: [RFC]: new set breakpoint pending and show breakpoint pending commands Reply-to: Eli Zaretskii References: <402974E1.8090909@redhat.com> X-SW-Source: 2004-02/txt/msg00277.txt.bz2 > Date: Tue, 10 Feb 2004 19:18:41 -0500 > From: Jeff Johnston > > I have included a doc patch but will wait on posting a change to pending.exp > until everyone is ok with the interface. A change is not required to make > pending.exp work, it would just exercise the new functionality. I have tested > the new settings manually. > > Ok? Thanks. A few minor comments about the documentation patch: > +If a specified breakpoint location cannot be found, it may due to the fact ^^^ I think there's a "be" missing at the spot I marked. > +that the location is in a shared library that is yet to be loaded. In such > +a case, you may want @value{GDBN} to create a special breakpoint (known as > +a pending breakpoint) that Please put "pending breakpoint", just this once, in @dfn{}, so that it stands out. (This is generally a good practice when introducing new terminology.) > When a breakpoint location is unrecognized, > +you are queried to see if a pending breakpoint should be created. I'd rephrase this slightly: When @value{GDBN} cannot find the breakpoint location, it queries you whether a pending breakpoint should be created. Otherwise, it can go in when the code patch is approved.