Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: keiths@cygnus.com
Cc: fnasser@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] breakpoint.c: don't generate bp events for internal bps
Date: Fri, 11 May 2001 08:04:00 -0000	[thread overview]
Message-ID: <3099-Fri11May2001180501+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <Pine.GSO.4.33.0105110704500.27065-100000@ryobi.cygnus.com>

> Date: Fri, 11 May 2001 07:08:31 -0700 (PDT)
> From: Keith Seitz <keiths@cygnus.com>
> 
> On Fri, 11 May 2001, Eli Zaretskii wrote:
> 
> > > 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?
> 
> Do the words "it's stupid" mean anything to you?

I looked them up ;-)

> From gdb-events.h:
> 
> /* User Interface Events.
>    Copyright 1999, 2000, 2001 Free Software Foundation, Inc.
> 
> "User Interface Events". User interfaces don't care about internal
> breakpoints -- only user-set breakpoints. IMO all of the breakpoints
> excluded from the event trigger are BACKEND breakpoints, and they should
> not ever be exposed to users (or non-backend code).
> 
> If someone writing ui code needs to know about internal breakpoints, he
> doing something wrong.

Sorry, I still don't get the relevance of this to what I asked.
Perhaps I'm stupid.


  reply	other threads:[~2001-05-11  8:04 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
2001-05-11  7:09     ` Keith Seitz
2001-05-11  8:04       ` Eli Zaretskii [this message]
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=3099-Fri11May2001180501+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