Eclipse Community Forums: Rich Client Platform (RCP) » Diagnosing "Unhandled Loop Exception"

Home » Eclipse Projects » Rich Client Platform (RCP) » Diagnosing "Unhandled Loop Exception"

Diagnosing "Unhandled Loop Exception" [message #460321]

Tue, 19 December 2006 18:36

Eclipse User

When one gets "Unhandled Loop Exception: Reason <blah>" on
error.out, is there some general way to go about diagnosing
the problem? I find no documentation at all on how to tell
where this exception is being thrown. It doesn't produce a
stack trace, and I find no way to make it do so, nor any
way to break on an exception to trap the throw. Searching
the Eclipse documentation finds nothing. Searching Google
finds lots of people diagnosing particular problems which
involve this, but nobody seems to answer the general question.

Thanks
jim

Re: Diagnosing "Unhandled Loop Exception" [message #460322 is a reply to message #460321]

Tue, 19 December 2006 18:42

Eclipse User

Jim Goodwin wrote:
> When one gets "Unhandled Loop Exception: Reason <blah>"....

I meant "Unhandled Event Loop Exception" of course...
sorry.

Re: Diagnosing "Unhandled Loop Exception" [message #460323 is a reply to message #460322]

Tue, 19 December 2006 19:17

Eclipse User

Originally posted by: remy.suen.gmail.com

Add '-consoleLog' to your "Program Arguments:" within your run
configuration. You should be able to see an actual stacktrace.

If all else fails just put a try-catch around the suspected code.

Regards,
Rem

Re: Diagnosing "Unhandled Loop Exception" [message #460337 is a reply to message #460321]

Wed, 20 December 2006 06:53

Eclipse User

Unhandled Loop Exceptions are Exceptions which get thrown in the UI
Loop. A lot of times the actual Exception that is causing this is logged
in the runtime log right after or before this exception is thrown. If
you don't have any other exception in your log your next best bet is
that your UI Code is doing something it shouldn't be doing so a good
start is to go into your ui code and start commenting out or wrapping it
in a try catch to see what exception is being thrown. Stepping into the
ui code with the debugger might also give you a clue.

Regards
Stefan

Jim Goodwin wrote:
> When one gets "Unhandled Loop Exception: Reason <blah>" on
> error.out, is there some general way to go about diagnosing
> the problem? I find no documentation at all on how to tell
> where this exception is being thrown. It doesn't produce a
> stack trace, and I find no way to make it do so, nor any
> way to break on an exception to trap the throw. Searching
> the Eclipse documentation finds nothing. Searching Google
> finds lots of people diagnosing particular problems which
> involve this, but nobody seems to answer the general question.
>
> Thanks
> jim

Re: Diagnosing "Unhandled Loop Exception" [message #460344 is a reply to message #460321]

Wed, 20 December 2006 11:07

Eclipse User

The -consoleLog suggestion was good. Also, eclipse should be logging
these in your error log.

http://wiki.eclipse.org/index.php/FAQ_Where_can_I_find_that_ elusive_.log_file%3F

Later,
PW

Re: Diagnosing "Unhandled Loop Exception" [message #460359 is a reply to message #460321]

Wed, 20 December 2006 13:04

Eclipse User

Thanks to all, that was a big help.

A suggestion for whoever deals with this sort of thing:
it would be nice if searching the Eclipse docs for
"Unhandled loop exception" found something explaining
what it means and referring to the logging capability
to diagnose it.

For me, "unhandled loop exception" had become Eclipse's
"general protection fault" error or "service engine soon"
idiot light: the one that happens all the time for all kinds
of different reasons, and isn't going to tell you anything
about what's really wrong. So just being able to find it
would help a lot.

Thanks for all help

jim

Previous Topic:	Cannot open editor - NoClassDefFound for MultiPageEditorPart
Next Topic:	How do I define a custom extension point?

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Mar 18 10:53:15 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter