[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[jdt-debug-dev] Re: [jdt-core-dev] Wrapping JDT
|
The event set does not indicate which breakpoint was hit, but it does
provide the thread that suspended. The thread then provides the associated
breakpoint(s).
@see IThread.getBreakpoints()
Darin
From:
100ji <itz100ji@xxxxxxxxx>
To:
jdt-core-dev@xxxxxxxxxxx
Date:
06/12/2009 12:30 AM
Subject:
[jdt-core-dev] Wrapping JDT
Sent by:
jdt-core-dev-bounces@xxxxxxxxxxx
Hi all,
I am working on a research project to develop a new user interface for
debuggers. Instead of writing my own debugger, I implemented an eclipse
plugin that wraps some of the interfaces exposed by the eclipse Java
debugger.Currently, I implemented a IDebugEventSetListener interface that
handles all the debug events that are produced by the eclipse debugger.
However, the debugger doesn't expose which breakpoint has caused the
thread to suspend. Is there a way to know which breakpoint(and it's type)
has caused the VM to suspend? More precisely, I want to know which
suspensions were caused by uncaught exceptions. I have gone through the
documentation and googled quite a bit, but there doesn't seem to be a way.
Any pointers in this directions will be helpful.
TIA,
-S-
_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jdt-core-dev
