From: "Martin M. Hunt" <hunt@redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: Insight Mailing List <insight@sources.redhat.com>
Subject: Re: [RFA] fix session breakpoints
Date: Thu, 03 Jan 2002 13:44:00 -0000 [thread overview]
Message-ID: <200201032144.NAA06996@cygnus.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0201021810480.3400-100000@makita.cygnus.com>
OK, Checked in with a lengthy explanation in the comments and
suggestions about how it could eventually be fixed to deal with
all cases.
Martin
On Wednesday 02 January 2002 06:13 pm, Keith Seitz wrote:
> On Wed, 2 Jan 2002, Martin M. Hunt wrote:
> > This is a second version of the patch that attempts to check if you are
> > debugging gdb with itself before ignoring those breakpoints. It assumes
> > the name of the executable starts with "gdb" or "insight". Of course
> > this isn't ideal either, but anything else will require GDB changes and
> > IMO will not be worth the effort.
>
> While I agree with Tom that it would be nice to fix this for real, I also
> acknowledge that there are for more people using sessions to do
> init-script like things than those using gdb's init files.
>
> What we really want is something in breakpoint.c to tell us if the
> breakpoint was set from an init script. Somehow I doubt we'd get it.
>
> Please add a comment about our failure to deal with this generically, but
> for now, we might as well make developers' lives easier. Then commit.
>
> Thanks,
> Keith
next prev parent reply other threads:[~2002-01-03 21:44 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
2002-01-02 12:48 ` Ian Roxborough
2002-01-02 18:14 ` Keith Seitz
2002-01-03 13:44 ` Martin M. Hunt [this message]
-- 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=200201032144.NAA06996@cygnus.com \
--to=hunt@redhat.com \
--cc=insight@sources.redhat.com \
--cc=keiths@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).