From: Tom Tromey <tromey@redhat.com>
To: "Martin M. Hunt" <hunt@redhat.com>
Cc: Insight Mailing List <insight@sources.redhat.com>
Subject: Re: [RFA] fix session breakpoints
Date: Wed, 02 Jan 2002 12:46:00 -0000 [thread overview]
Message-ID: <87d70ssc5g.fsf@creche.redhat.com> (raw)
In-Reply-To: "Martin M. Hunt"'s message of "Wed, 2 Jan 2002 12:42:10 -0800"
>>>>> "Martin" == Martin M Hunt <hunt@redhat.com> writes:
Martin> This is a second version of the patch that attempts to check
Martin> if you are debugging gdb with itself before ignoring those
Martin> breakpoints. It assumes the name of the executable starts
Martin> with "gdb" or "insight". Of course this isn't ideal either,
Martin> but anything else will require GDB changes and IMO will not be
Martin> worth the effort.
Won't we run into this problem with any project that sets breakpoints
in .gdbinit?
Could we detect whether any breakpoints are set before setting the
session breakpoints and then avoid saving just those?
Tom
next prev parent reply other threads:[~2002-01-02 20:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-02 12:42 Martin M. Hunt
2002-01-02 12:46 ` Tom Tromey [this message]
2002-01-02 12:48 ` Ian Roxborough
2002-01-02 18:14 ` Keith Seitz
2002-01-03 13:44 ` Martin M. Hunt
-- strict thread matches above, loose matches on Subject: below --
2001-10-13 11:41 Martin M. Hunt
2001-12-17 14:49 ` Martin M. Hunt
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=87d70ssc5g.fsf@creche.redhat.com \
--to=tromey@redhat.com \
--cc=hunt@redhat.com \
--cc=insight@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).