From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26139 invoked by alias); 3 Dec 2003 16:06:43 -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 26123 invoked from network); 3 Dec 2003 16:06:41 -0000 Received: from unknown (HELO gollum.inter.net.il) (192.114.186.22) by sources.redhat.com with SMTP; 3 Dec 2003 16:06:41 -0000 Received: from zaretski ([80.230.144.52]) by gollum.inter.net.il (Mirapoint Messaging Server MOS 3.3.8-GR) with ESMTP id BZF00484; Wed, 3 Dec 2003 18:05:12 +0200 (IST) Date: Wed, 03 Dec 2003 16:06:00 -0000 From: "Eli Zaretskii" To: "J. Johnston" Message-Id: <3405-Wed03Dec2003180427+0200-eliz@elta.co.il> CC: gdb-patches@sources.redhat.com In-reply-to: <3FCD3DC5.8000308@redhat.com> (jjohnstn@redhat.com) Subject: Re: [RFC]: pending break support Reply-to: Eli Zaretskii References: <3FCD3DC5.8000308@redhat.com> X-SW-Source: 2003-12/txt/msg00078.txt.bz2 > Date: Tue, 02 Dec 2003 20:35:01 -0500 > From: "J. Johnston" > > I have added documentation on the pending breakpoint per Eli's request. Thanks. The documentation patch is approved, but please take care of these minor problems: > +Where the breakpoint is in your program, as a memory address. If the > +breakpoint is pending on a future load of a shared library, the address > +will be listed as . First, please add something like "(see below)" after "If the breakpoint is pending", since this is the first time the reader meets this term. Second, please say @samp{} to make this stand out. > +@cindex pending breakpoints > +If a specified breakpoint location cannot be found, you will be prompted > +as to whether you want to make the breakpoint pending on a future shared > +library load. This is useful for setting breakpoints at the start of your > +@value{GDBN} session for locations that you know will be dynamically loaded > +later by the program being debugged. > +You may specify > +a condition for a pending breakpoint, however, the > +condition will only be parsed for correctness after the breakpoint location > +is resolved by a future shared library load. A pending breakpoint can be > +enabled or disabled. A disabled pending breakpoint will not be resolved > +on subsequent shared library loads. Enabling a disabled pending breakpoint > +will cause @value{GDBN} to attempt to resolve the breakpoint in the event > +that the required shared library has already been loaded. > +Once a shared library load resolves a pending breakpoint location, the > +pending breakpoint is removed and a real breakpoint is created. I think this text should be divided into several paragraphs, as it describes several not-so-related aspects of a pending breakpoint. TIA