[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: SET BREAK/CALL equiv. on gdb
From: |
Paul Gilliam |
Subject: |
Re: SET BREAK/CALL equiv. on gdb |
Date: |
Wed, 15 Sep 2004 09:44:24 -0700 |
address@hidden wrote on 09/14/2004 11:44:33
PM:
> > Date: Tue, 14 Sep 2004 07:24:56 -0400
> > From: Michael Chastain <address@hidden>
> > Cc:
> >
> > address@hidden 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
> address@hidden
> 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 #=-