🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: gnu.gdb.bug
Article #1321

Re: SET BREAK/CALL equiv. on gdb

#1321
From: Paul Gilliam
Date: Wed, 15 Sep 2004 16:44
43 lines
3087 bytes
bug-gdb-bounces+gilliam=us.ibm.com@gnu.org wrote on 09/14/2004 11:44:33 
PM:

> > Date: Tue, 14 Sep 2004 07:24:56 -0400
> > From: Michael Chastain <mec.gnu@mindspring.com>
> > Cc: 
> > 
> > UHAP023@alpha1.rhbnc.ac.uk wrote:
> > > There is a very useful feature of the DEC(RIP!) VMS debugger which
> > > will do a break on every function call.  Is there any equivalent in
> > > gdb, short of using 'info function', parsing the output to get a 
list
> > > of all functions in the code and then generating separate break
> > > instructions for them all?  Needless to say, this is very tedious...
> > 
> > Alas, no, there isn't.
> 
> I think "rbreak ." should do the trick.
> 
> 
> _______________________________________________
> Bug-gdb mailing list
> Bug-gdb@gnu.org
> http://lists.gnu.org/mailman/listinfo/bug-gdb

All most.  It would be nice if it where possible to manage all those 
break-points together.  One 'disable' for the whole bunch.  Of course the 
user could "rbreak .", note the numbers of the first new breakpoint and 
the last, then use that range: "disable <n>-<m>" (is that right syntax?).

Maybe what we want is to be able to name (automatically?) a range of 
breakpoints.  Something like:

gdb> rbreak .
bp group "functionsBP" is 2-234
gdb> disable functionsBP
breakpoints 2-234 disabled
gdb> 

Just a thought.


-=# Paul Gilliam #=-
Technical Details
Message-ID: <mailman.2871.1095267162.1998.bug-gdb@gnu.org>
Path: arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!news1.google.com!newsfeed.stanford.edu!shelby.stanford.edu!not-for-mail

Show Full Headers
Complete Article Headers
X-Google-Thread: f5053,c64115f384ece791
X-Google-Attributes: gidf5053,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!news1.google.com!newsfeed.stanford.edu!shelby.stanford.edu!not-for-mail
From: Paul Gilliam <gilliam@us.ibm.com>
Newsgroups: gnu.gdb.bug
Subject: Re: SET BREAK/CALL equiv. on gdb
Date: Wed, 15 Sep 2004 09:44:24 -0700
Lines: 45
Approved: bug-gdb@gnu.org
Message-ID: <mailman.2871.1095267162.1998.bug-gdb@gnu.org>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-Trace: news.Stanford.EDU 1095266813 26123 199.232.76.165 (15 Sep 2004 16:46:53 GMT)
X-Complaints-To: news@news.stanford.edu
Cc: bug-gdb-bounces+gilliam=us.ibm.com@gnu.org, gnu-gdb-bug@moderators.isc.org,
 UHAP023@alpha1.rhbnc.ac.uk
To: Eli Zaretskii <eliz@gnu.org>
Envelope-to: bug-gdb@gnu.org
In-Reply-To: <01c49aef$Blat.v2.2.2$9b00d200@zahav.net.il>
X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003
X-MIMETrack: Serialize by Router on D03NM113/03/M/IBM(Release 6.51HF338 | June
 21, 2004) at 09/15/2004 10:44:36,
 Serialize complete at 09/15/2004 10:44:36
X-BeenThere: bug-gdb@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Bug reports for GDB, the GNU debugger" <bug-gdb.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-gdb>,
 <mailto:bug-gdb-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-gdb>
List-Post: <mailto:bug-gdb@gnu.org>
List-Help: <mailto:bug-gdb-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-gdb>,
 <mailto:bug-gdb-request@gnu.org?subject=subscribe>