From: Tom Tromey <tromey@redhat.com>
To: RT <mfoc73@dsl.pipex.com>
Cc: "'Atul Talesara'" <atul.talesara@nevisnetworks.com>,
"'Hareesh Nagarajan'" <hnagaraj@cs.uic.edu>,
"'GDB'" <gdb@sources.redhat.com>
Subject: Re: Is it possible to save breakpoints to a file?
Date: Fri, 11 Mar 2005 01:28:00 -0000 [thread overview]
Message-ID: <m3r7in7z3p.fsf@localhost.localdomain> (raw)
In-Reply-To: <423070F6.40500@dsl.pipex.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
next prev parent reply other threads:[~2005-03-11 1:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 10:52 Atul Talesara
2005-03-10 15:08 ` Kris Warkentin
2005-03-10 15:52 ` Dave Korn
2005-03-10 16:08 ` RT
2005-03-11 1:28 ` Tom Tromey [this message]
2005-03-12 11:29 ` RT
2005-03-12 11:58 ` Russell Shaw
2005-03-12 12:13 ` RT
2005-03-12 19:39 ` Tom Tromey
-- strict thread matches above, loose matches on Subject: below --
2005-03-13 5:03 Paul Schlie
2005-03-10 7:07 Hareesh Nagarajan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3r7in7z3p.fsf@localhost.localdomain \
--to=tromey@redhat.com \
--cc=atul.talesara@nevisnetworks.com \
--cc=gdb@sources.redhat.com \
--cc=hnagaraj@cs.uic.edu \
--cc=mfoc73@dsl.pipex.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox