This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA] breakpoint.c: don't generate bp events for internal bps
- To: Eli Zaretskii <eliz at is dot elta dot co dot il>
- Subject: Re: [RFA] breakpoint.c: don't generate bp events for internal bps
- From: Keith Seitz <keiths at cygnus dot com>
- Date: Fri, 11 May 2001 07:08:31 -0700 (PDT)
- cc: <fnasser at redhat dot com>, <gdb-patches at sources dot redhat dot 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? 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.
Keith