Eclipse Community Forums: Eclipse Platform

Home » Eclipse Projects » Eclipse Platform » plug-in debugging

Mon, 25 October 2004 13:19

Eclipse User

Originally posted by: berta_hauri.hotmail.com

I'm currently developing my first plug-in project and I would appreciate
it if someone could give me a hint how I can efficiently debug my plug-in.

Currently I'm debugging my plug-in by launching a run-time workbench in a
debug mode. But my problem is that I just get messages like "unable to
create part" when I try to open my view in the run-time workbench. I don't
get any exceptions or System.out.println statements in the console. (If
the plug-in works then the System.out.println statements are written to
the console without a problem)
How can I find the exact line where the error occured? What kind of
techniques do you use to debug? I tried to set breakpoints but I'm not
able to find the location where the program actually fails.

I'm really looking forward to some hints.
Thanks Berta

Re: plug-in debugging [message #274583 is a reply to message #274577]

Mon, 25 October 2004 17:02

Eclipse User

The exception stack trace will be in the .log file for the target workspace.
Your easiest option is to specify -consolelog as a program argument when
debugging using the run-time workbench

HTH
Darins

"Berta Hauri" <berta_hauri@hotmail.com> wrote in message
news:cljci9$2ia$1@eclipse.org...
> I'm currently developing my first plug-in project and I would appreciate
> it if someone could give me a hint how I can efficiently debug my plug-in.
>
> Currently I'm debugging my plug-in by launching a run-time workbench in a
> debug mode. But my problem is that I just get messages like "unable to
> create part" when I try to open my view in the run-time workbench. I don't
> get any exceptions or System.out.println statements in the console. (If
> the plug-in works then the System.out.println statements are written to
> the console without a problem)
> How can I find the exact line where the error occured? What kind of
> techniques do you use to debug? I tried to set breakpoints but I'm not
> able to find the location where the program actually fails.
>
> I'm really looking forward to some hints.
> Thanks Berta
>

Previous Topic:	accessing sourceforge CVS repository behind a firewall
Next Topic:	config.ini complete reference

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 26 20:24:50 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter