Re: Is it possible to save breakpoints to a file?

Re: Is it possible to save breakpoints to a file?

[Paul Schlie]

> Russell Shaw writes:
>> RT wrote:
>>> Tom Tromey wrote:
>>> I don't know if this is in the gdb bug database; it should be.
>>
>> I haven't looked at this in detail. I suspect the problem is that Insigh
>> is no longer actively maintained, and so it's difficult to get a version of
>> insight that uses the current gdb.
>>
>> There's no point filing bugs that are Insight-specific; there's no one to
>> work on them. A trivial licensing problem has lead to gdb having no usable
>> GUI (that I know of, anyway; and I've used both ddd and insight). If anyone
>> at the FSF knows of a way to debug multi-threaded shared-library apps without
>> a GUI, then I'd be really pleased to hear from them. And, if I don't hear
>> from them, I guess that they'll agree that gdb is an 80's dinosaur, and it's
>> time to put it to bed.
>
> What is the licencing problem? I've been going to make a new gui for
> gdb, but i'm busy with too much other stuff.

For what it's worth, although Insight may not be "actively" maintained, it
still seems to get periodic attention from Keith Seitz and a few other as
opportunity seems to allow. And believe it or not, basically work fine for
cross target debugging on OSX, and prefer it vs most other's (although it
would be nice to figure out some why to hook Apples Xcode debugger interface
into a cross targeted configured gdb).  So might be worth at least noting
the bug? (may get lucky).

   http://sources.redhat.com/insight/

RE: Is it possible to save breakpoints to a file?

[Atul Talesara]

> Is it possible to save all breakpoints that one
> sets to a file, so that 
> we can reload the breakpoints set during the next
> debug run?
Well, though not exactly the same ... this might
solve your problem. You can have a plain text
file that can list all the breakpoints you want
to put. Ex:
$ cat breakpoints
break code_file_01.c : 515
break code_file_02.c : 5
break code_file_03.c : 201

And then you can source this file to gdb as:
(gdb) source breakpoints

In fact you can have *any* command you wish in the
sourced file. If you put all these in '.gdbinit'
file then gdb will automatically source this on start up!
Hope this addresses your need.

Regards,
Atul
http://the-shaolin.blogspot.com/
---------------------------------------------------------- 
You can tell more about a person by what he says about
others than you can by what others say about him.

---------------------------------------------------------- 

Re: Is it possible to save breakpoints to a file?

[Kris Warkentin]

Another possiblity is to use the logging abilities and define your own.

define save-breaks
set logging file $arg0
set logging on
info breakpoints
set logging off
end

Unfortunately this doesn't give you something that you can load later so 
you'd have to write a little bit of an awk script to process it into an 
init file.

cheers,

Kris

Atul Talesara wrote:

>>Is it possible to save all breakpoints that one
>>sets to a file, so that 
>>we can reload the breakpoints set during the next
>>debug run?
>>    
>>
>Well, though not exactly the same ... this might
>solve your problem. You can have a plain text
>file that can list all the breakpoints you want
>to put. Ex:
>$ cat breakpoints
>break code_file_01.c : 515
>break code_file_02.c : 5
>break code_file_03.c : 201
>
>And then you can source this file to gdb as:
>(gdb) source breakpoints
>
>In fact you can have *any* command you wish in the
>sourced file. If you put all these in '.gdbinit'
>file then gdb will automatically source this on start up!
>Hope this addresses your need.
>
>Regards,
>Atul
>http://the-shaolin.blogspot.com/
>---------------------------------------------------------- 
>You can tell more about a person by what he says about
>others than you can by what others say about him.
>
>---------------------------------------------------------- 
>  
>

RE: Is it possible to save breakpoints to a file?

[Dave Korn]

----Original Message----
>From: Atul Talesara
>Sent: 10 March 2005 10:53

>> Is it possible to save all breakpoints that one
>> sets to a file, so that
>> we can reload the breakpoints set during the next
>> debug run?
> Well, though not exactly the same 

  [... snip ...]

> In fact you can have *any* command you wish in the
> sourced file. If you put all these in '.gdbinit'
> file then gdb will automatically source this on start up!

  If you are using the insight GUI for gdb, that will save your breakpoints
for you as part of the project preferences.  It writes them into .gdbinit
automatically and reloads them next time you're debugging the same
executable.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....

Re: Is it possible to save breakpoints to a file?

[RT]

Dave Korn wrote:

>   If you are using the insight GUI for gdb, that will save your breakpoints
> for you as part of the project preferences.  It writes them into .gdbinit
> automatically and reloads them next time you're debugging the same
> executable.

Which makes life rather difficult if you have a break set in a shared 
library. If you reply 'yes' by mistake when Insight asks if you want to 
make the break pending on the library load, then gdb will rapidly crash.

- Richard

Re: Is it possible to save breakpoints to a file?

[Tom Tromey]

>>>>> "RT" == RT  <mfoc73@dsl.pipex.com> writes:

>> If you are using the insight GUI for gdb, that will save your breakpoints
>> for you as part of the project preferences.  It writes them into .gdbinit
>> automatically and reloads them next time you're debugging the same
>> executable.

RT> Which makes life rather difficult if you have a break set in a shared
RT> library. If you reply 'yes' by mistake when Insight asks if you want
RT> to make the break pending on the library load, then gdb will rapidly
RT> crash.

I don't know if this is in the gdb bug database; it should be.

More importantly, Insight should probably automatically set all
restored breakpoints to be pending breakpoints as needed, without
asking the user.  Presumably if they were saved, then they once
existed.  Making them pending seems like a UI improvement without much
downside.  (You might carry stale pending breakpoints around, say if
you delete a function that had a breakpoint in it.  But you probably
also won't care.)

Tom

Re: Is it possible to save breakpoints to a file?

[RT]

Tom Tromey wrote:
>>>>>>"RT" == RT  <mfoc73@dsl.pipex.com> writes:
> 
> 
>>>If you are using the insight GUI for gdb, that will save your breakpoints
>>>for you as part of the project preferences.  It writes them into .gdbinit
>>>automatically and reloads them next time you're debugging the same
>>>executable.
> 
> 
> RT> Which makes life rather difficult if you have a break set in a shared
> RT> library. If you reply 'yes' by mistake when Insight asks if you want
> RT> to make the break pending on the library load, then gdb will rapidly
> RT> crash.
> 
> I don't know if this is in the gdb bug database; it should be.

I haven't looked at this in detail. I suspect the problem is that 
Insight is no longer actively maintained, and so it's difficult to get a 
version of insight that uses the current gdb.

There's no point filing bugs that are Insight-specific; there's no one 
to work on them. A trivial licensing problem has lead to gdb having no 
usable GUI (that I know of, anyway; and I've used both ddd and insight). 
If anyone at the FSF knows of a way to debug multi-threaded 
shared-library apps without a GUI, then I'd be really pleased to hear 
from them. And, if I don't hear from them, I guess that they'll agree 
that gdb is an 80's dinosaur, and it's time to put it to bed.

- Richard

Re: Is it possible to save breakpoints to a file?

[Russell Shaw]

RT wrote:
> Tom Tromey wrote:
> 
>>>>>>> "RT" == RT  <mfoc73@dsl.pipex.com> writes:
>>
>>>> If you are using the insight GUI for gdb, that will save your 
>>>> breakpoints
>>>> for you as part of the project preferences.  It writes them into 
>>>> .gdbinit
>>>> automatically and reloads them next time you're debugging the same
>>>> executable.
>>
>> RT> Which makes life rather difficult if you have a break set in a shared
>> RT> library. If you reply 'yes' by mistake when Insight asks if you want
>> RT> to make the break pending on the library load, then gdb will rapidly
>> RT> crash.
>>
>> I don't know if this is in the gdb bug database; it should be.
> 
> I haven't looked at this in detail. I suspect the problem is that 
> Insight is no longer actively maintained, and so it's difficult to get a 
> version of insight that uses the current gdb.
> 
> There's no point filing bugs that are Insight-specific; there's no one 
> to work on them. A trivial licensing problem has lead to gdb having no 
> usable GUI (that I know of, anyway; and I've used both ddd and insight). 
> If anyone at the FSF knows of a way to debug multi-threaded 
> shared-library apps without a GUI, then I'd be really pleased to hear 
> from them. And, if I don't hear from them, I guess that they'll agree 
> that gdb is an 80's dinosaur, and it's time to put it to bed.

What is the licencing problem? I've been going to make a new gui for
gdb, but i'm busy with too much other stuff.

Re: Is it possible to save breakpoints to a file?

[RT]

Russell Shaw wrote:
> RT wrote:
> 
>> Tom Tromey wrote:
>>
>>>>>>>> "RT" == RT  <mfoc73@dsl.pipex.com> writes:
>>>
>>>
>>>>> If you are using the insight GUI for gdb, that will save your 
>>>>> breakpoints
>>>>> for you as part of the project preferences.  It writes them into 
>>>>> .gdbinit
>>>>> automatically and reloads them next time you're debugging the same
>>>>> executable.
>>>
>>>
>>> RT> Which makes life rather difficult if you have a break set in a 
>>> shared
>>> RT> library. If you reply 'yes' by mistake when Insight asks if you want
>>> RT> to make the break pending on the library load, then gdb will rapidly
>>> RT> crash.
>>>
>>> I don't know if this is in the gdb bug database; it should be.
>>
>>
>> I haven't looked at this in detail. I suspect the problem is that 
>> Insight is no longer actively maintained, and so it's difficult to get 
>> a version of insight that uses the current gdb.
>>
>> There's no point filing bugs that are Insight-specific; there's no one 
>> to work on them. A trivial licensing problem has lead to gdb having no 
>> usable GUI (that I know of, anyway; and I've used both ddd and 
>> insight). If anyone at the FSF knows of a way to debug multi-threaded 
>> shared-library apps without a GUI, then I'd be really pleased to hear 
>> from them. And, if I don't hear from them, I guess that they'll agree 
>> that gdb is an 80's dinosaur, and it's time to put it to bed.
> 
> 
> What is the licencing problem? I've been going to make a new gui for
> gdb, but i'm busy with too much other stuff.

I'm not sure of the details. Basically, it seems that RH wants to donate 
  Insight to the FSF, but the FSF doesn't want it, for what appear to be 
ideological reasons. There are probably others on this list who have a 
much better idea of the problem than I have.

- Richard

Re: Is it possible to save breakpoints to a file?

[Tom Tromey]

>>>>> "RT" == RT  <mfoc73@dsl.pipex.com> writes:

RT> I haven't looked at this in detail. I suspect the problem is that
RT> Insight is no longer actively maintained, and so it's difficult to get
RT> a version of insight that uses the current gdb.

You can still build insight out of cvs.  It will then use the current
gdb.

RT> A trivial licensing problem has lead to gdb having no
RT> usable GUI (that I know of, anyway; and I've used both ddd and
RT> insight).

There are actually quite a few gdb UIs, in addition to Insight and
DDD.  Maybe MI made it too easy to write gdb UIs :-)

There's one written in Ada whose name I forget.

Eclipse also comes with a gdb GUI.  (The Eclipse one is interesting
because, AIUI, it saves breakpoints more intelligently, as markers in
your source.)

Apple also has one in their IDE, but I know little about it.

Finally, Anjuta[1] has one and KDevelop[2] has one.

I haven't used most of these, and whether they meet your "usable"
qualification is subjective...

Tom

[1] http://anjuta.sourceforge.net/
[2] http://www.kdevelop.org/

Is it possible to save breakpoints to a file?

[Hareesh Nagarajan]

Hi,

Is it possible to save all breakpoints that one sets to a file, so that 
we can reload the breakpoints set during the next debug run?

Thanks,

Hareesh