Re: [cdt-debug-dev] special breakpoint and event

["Mikhail Khodjaiants" <mikhailk@xxxxxxx>]

Actaully, Alain is the right person to comment on this.
Each element of the CDT debug model (targets, threads, stack frames,
variables, etc.) registers itself as a CDI events listener. The event
handlers notify the UI components.
If you want to prevent UI updates in some situations you should suppress the
firing of CDI events. This could be done when gdb stops at your special
breakpoints. Take a look at the
"org.eclipse.cdt.debug.mi.core.EventThread.java" class.

----- Original Message ----- 
From: "Thomas Fletcher" <ThomasF@xxxxxxx>
To: <cdt-debug-dev@xxxxxxxxxxx>
Sent: Friday, May 21, 2004 7:20 AM
Subject: RE: [cdt-debug-dev] special breakpoint and event


>
>
> > -----Original Message-----
> > From: Bob Lewis [mailto:bobl_1970@xxxxxxxxx]
> > Sent: Thursday, May 20, 2004 8:16 PM
> > To: cdt-debug-dev@xxxxxxxxxxx
> > Subject: Re: [cdt-debug-dev] special breakpoint and event
> >
> >
> > --- Mikhail Khodjaiants <mikhailk@xxxxxxx> wrote:
> > > I don't think it is posible to implement an
> > > extension for this particular
> > > case in the current CDT architecture.
> > > In this version there is no mechanism to suppress
> > > some events fired by debug
> > > engines. The idea to support "silent" breakpoints
> > > has been discussed for
> > > different reasons, but nothing has been implemented.
> >
> > Bad news for me! So if I have to modify the current
> > CDT to achive what I want, what classes should I pay
> > attention?
>
> Bad news, good news.  If you submit a patch for this kind
> of modification, then not only will it suit your needs exactly,
> but if will be maintained and carried forward in the future
> so that others can take advantage of it.
>
> I'll let Mikhail comment on the actual ins and outs.
>
> Thanks,
>  Thomas
> _______________________________________________
> cdt-debug-dev mailing list
> cdt-debug-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
>