[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[List Home]
|
[jdt-core-dev] Wrapping JDT
|
- From: 100ji <itz100ji@xxxxxxxxx>
- Date: Fri, 12 Jun 2009 01:24:34 -0400
- Delivered-to: jdt-core-dev@eclipse.org
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=E1Pv3c7FDU0amXIhlzd0MgTXfjacJunyGuLM5jaDROU=; b=CHDoshmUFcwA4eZgiArxu40GIA0ImGAPVftb9MUhTinHLuQbOcsGrn5iSPpcsu67Uj 0O8xeK+LY1s6Hk4QWuSf1L/nXvfIAFG3vIR64m9xb4NR4elIQ3WcIf/4rzK8ScjP7dkp JAqlEpIjeml4ezEY5BAKJfSJsYZ+is8y8nVYQ=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=i/eZY+UM1ggSe9fnro/PBYZMg+niVReh5wTv6DWVSThx4B8v0UZUAgncunRMErxZGo LU/s5dcIw61iKW1M7778ywjyr/NAW77tgVHADzyaSRzBNTwdP1eskqnoND8eMGSIy6bW QRakERQe1ImauBR4xHWIKUW5aMT4NmWpxDIIw=
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-