From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: fnasser@redhat.com
Cc: keiths@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] breakpoint.c: don't generate bp events for internal bps
Date: Thu, 10 May 2001 23:56:00 -0000 [thread overview]
Message-ID: <3405-Fri11May2001095555+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <3AFB779D.E9F4B5D3@redhat.com>
> Date: Fri, 11 May 2001 01:24:45 -0400
> From: Fernando Nasser <fnasser@redhat.com>
>
> It is OK to only generate events for visible breakpoints, but the hook
> must run for all breakpoints. Whatever is using the hook may need to
> know about the internal ones as well.
I agree. But I would go even farther: is it possible to explain why
is it a good idea to make this change? What exactly is wrong with
generating breakpoint events as we do now?
At the very least, I think we should consider all the uses of the
breakpoint events, to judge whether some of them do indeed want to see
internal breakpoints. Is such a list available somewhere?
next prev parent reply other threads:[~2001-05-10 23:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.33.0105102023220.29679-100000@ryobi.cygnus.com>
2001-05-10 22:26 ` Fernando Nasser
2001-05-10 23:56 ` Eli Zaretskii [this message]
2001-05-11 7:09 ` Keith Seitz
2001-05-11 8:04 ` Eli Zaretskii
2001-05-11 8:14 ` Keith Seitz
2001-05-11 9:57 ` Eli Zaretskii
2001-05-11 7:05 ` Keith Seitz
2001-05-11 8:54 ` Fernando Nasser
2001-05-11 18:56 ` Andrew Cagney
[not found] <Pine.GSO.4.33.0105110855100.9875-100000@ryobi.cygnus.com>
2001-05-11 9:15 ` Fernando Nasser
2001-05-11 10:22 ` Michael Snyder
2001-05-11 10:25 ` Fernando Nasser
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=3405-Fri11May2001095555+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=keiths@cygnus.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