From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eli Zaretskii" 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 Message-id: <3099-Fri11May2001180501+0300-eliz@is.elta.co.il> References: X-SW-Source: 2001-05/msg00209.html > Date: Fri, 11 May 2001 07:08:31 -0700 (PDT) > From: Keith Seitz > > On Fri, 11 May 2001, Eli Zaretskii wrote: > > > > Date: Fri, 11 May 2001 01:24:45 -0400 > > > From: Fernando Nasser > > > > > > 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.