Home » Eclipse Projects » Eclipse Platform » Eclipse Debug events and halt states
| Eclipse Debug events and halt states [message #152555] |
Mon, 03 November 2003 14:04  |
Eclipse User |
|
|
|
I'm implementing a debugger and I'm unable to discern between halting for
a breakpoint vs. stepping (this information isn't reliably exposed to me)
So far, it doesn't seem to impact the UI or interactions with the user, at
least within my debugger. It seems I should be firing the correct events,
and I don't know who else might be listening. Is there any chance I'll
run into trouble here if, say, I'm always using the BREAKPOINT event, even
if it was a step or a user suspend which caused the halt??
Thanks,
Adam
|
|
| |
| Re: Eclipse Debug events and halt states [message #152826 is a reply to message #152555] |
Tue, 04 November 2003 13:14  |
| Eclipse User |
|
|
|
There is no "breakpoint" event. There is a suspend event, with a detail that
tells why the suspend happened - a breakpoint or a step, etc.
Darin
"Adam Peller" <apeller@us.ibm.com> wrote in message
news:bo68sr$qq$1@eclipse.org...
> I'm implementing a debugger and I'm unable to discern between halting for
> a breakpoint vs. stepping (this information isn't reliably exposed to me)
> So far, it doesn't seem to impact the UI or interactions with the user, at
> least within my debugger. It seems I should be firing the correct events,
> and I don't know who else might be listening. Is there any chance I'll
> run into trouble here if, say, I'm always using the BREAKPOINT event, even
> if it was a step or a user suspend which caused the halt??
>
> Thanks,
> Adam
>
>
|
|
|
| Re: Eclipse Debug events and halt states [message #153106 is a reply to message #152826] |
Wed, 05 November 2003 11:14 |
| Eclipse User |
|
|
|
Yes, sorry, this is what I meant. Given that I cannot make the
distinction, I am faced with using something like "BREAKPOINT" for detail,
regardless of the actual cause (vs. stepping, client request). Just
wondering if any Eclipse code (outside of my own) actually cares what's in
this event. I'm assuming it isn't required for some sort of debugger
state information or UI.
Thanks,
Adam
Darin Wright wrote:
> There is no "breakpoint" event. There is a suspend event, with a detail that
> tells why the suspend happened - a breakpoint or a step, etc.
> Darin
> "Adam Peller" <apeller@us.ibm.com> wrote in message
> news:bo68sr$qq$1@eclipse.org...
> > I'm implementing a debugger and I'm unable to discern between halting for
> > a breakpoint vs. stepping (this information isn't reliably exposed to me)
> > So far, it doesn't seem to impact the UI or interactions with the user, at
> > least within my debugger. It seems I should be firing the correct events,
> > and I don't know who else might be listening. Is there any chance I'll
> > run into trouble here if, say, I'm always using the BREAKPOINT event, even
> > if it was a step or a user suspend which caused the halt??
> >
> > Thanks,
> > Adam
> >
> >
|
|
|
| Re: Eclipse Debug events and halt states [message #153532 is a reply to message #153106] |
Thu, 06 November 2003 09:41 |
| Eclipse User |
|
|
|
The debugger will automatically switch to or open the debug perspective when
a breakpoint is hit, and the window containing the debugger will be
activated (i.e. flash on Windows).
Darin
"Adam Peller" <apeller@us.ibm.com> wrote in message
news:bob7le$f07$1@eclipse.org...
> Yes, sorry, this is what I meant. Given that I cannot make the
> distinction, I am faced with using something like "BREAKPOINT" for detail,
> regardless of the actual cause (vs. stepping, client request). Just
> wondering if any Eclipse code (outside of my own) actually cares what's in
> this event. I'm assuming it isn't required for some sort of debugger
> state information or UI.
>
> Thanks,
>
> Adam
>
> Darin Wright wrote:
>
> > There is no "breakpoint" event. There is a suspend event, with a detail
that
> > tells why the suspend happened - a breakpoint or a step, etc.
>
> > Darin
>
> > "Adam Peller" <apeller@us.ibm.com> wrote in message
> > news:bo68sr$qq$1@eclipse.org...
> > > I'm implementing a debugger and I'm unable to discern between halting
for
> > > a breakpoint vs. stepping (this information isn't reliably exposed to
me)
> > > So far, it doesn't seem to impact the UI or interactions with the
user, at
> > > least within my debugger. It seems I should be firing the correct
events,
> > > and I don't know who else might be listening. Is there any chance
I'll
> > > run into trouble here if, say, I'm always using the BREAKPOINT event,
even
> > > if it was a step or a user suspend which caused the halt??
> > >
> > > Thanks,
> > > Adam
> > >
> > >
>
>
|
|
|
Goto Forum:
Current Time: Mon Nov 03 20:43:50 EST 2025
Powered by FUDForum. Page generated in 0.04698 seconds |
Home