This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Is it possible to save breakpoints to a file?
- From: Tom Tromey <tromey at redhat dot com>
- To: RT <mfoc73 at dsl dot pipex dot com>
- Cc: "'Atul Talesara'" <atul dot talesara at nevisnetworks dot com>, "'Hareesh Nagarajan'" <hnagaraj at cs dot uic dot edu>, "'GDB'" <gdb at sources dot redhat dot com>
- Date: 10 Mar 2005 18:25:30 -0700
- Subject: Re: Is it possible to save breakpoints to a file?
- References: <SERRANObeUzmRf6Ci6n00000027@SERRANO.CAM.ARTIMI.COM><423070F6.40500@dsl.pipex.com>
- Reply-to: tromey at redhat dot com
>>>>> "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