[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jdt-core-dev] Wrapping JDT
|
The interface you listed is not Java specific. If the question is only
about the debugger then you should post to eclipse.platform, otherwise to
eclipse.tools.jdt.
Dani
|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|100ji <itz100ji@xxxxxxxxx> |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|"Eclipse JDT Core developers list." <jdt-core-dev@xxxxxxxxxxx> |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|12.06.2009 08:51 |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Re: [jdt-core-dev] Wrapping JDT |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
Dani,
Sorry for posting it in the wrong place. Please let me know which newsgroup
is more appropriate for such questions?
Thanks,
-S-
On Fri, Jun 12, 2009 at 2:32 AM, Daniel Megert <daniel_megert@xxxxxxxxxx>
wrote:
You better ask this Debug question on the newsgroup. This list is for the
developers of JDT Core.
Dani
|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|100ji <itz100ji@xxxxxxxxx>
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|jdt-core-dev@xxxxxxxxxxx
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|12.06.2009 07:24
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|[jdt-core-dev] Wrapping JDT
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
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
_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jdt-core-dev
_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jdt-core-dev
