Uncaught Runtime Exceptions [message #319099] |
Sat, 11 August 2007 16:47  |
Eclipse User |
|
|
|
I have been using a couple of my own Runtime exceptions, LogicError and
DataIntegrity error(both of which extend RuntimeException), for catching
programming errors.
In 3.1 they did what I expected, that is, when thrown they terminated
execution and offered a stack trace showing the Exception message.
In 3.2.2 that is not happening. A dialog pops up, says a LogicException
has occurred, but does not show the exception's message or offer a
stack trace (the details >> page shows the same cryptic info).
1. Is there a way to obtain the stack trace when your code throws
runtime exceptions?
2. Is there a way to handle uncaught exceptions in your application,
that is, can one plug in a custom uncaught-exception handler?
I've searched the online help, google, and my books, with no luck,
Thanks,
Bill.
|
|
|
Re: Uncaught Runtime Exceptions [message #319100 is a reply to message #319099] |
Sat, 11 August 2007 16:49   |
Eclipse User |
|
|
|
Bill Winspur wrote:
> I have been using a couple of my own Runtime exceptions, LogicError and
> DataIntegrity error(both of which extend RuntimeException), for catching
> programming errors.
>
> In 3.1 they did what I expected, that is, when thrown they terminated
> execution and offered a stack trace showing the Exception message.
>
> In 3.2.2 that is not happening. A dialog pops up, says a LogicException
> has occurred, but does not show the exception's message or offer a
> stack trace (the details >> page shows the same cryptic info).
>
> 1. Is there a way to obtain the stack trace when your code throws
> runtime exceptions?
>
> 2. Is there a way to handle uncaught exceptions in your application,
> that is, can one plug in a custom uncaught-exception handler?
>
> I've searched the online help, google, and my books, with no luck,
>
> Thanks,
>
> Bill.
Sorry, the problem I'm having is on 3.3, not 3.2.2, Bill
|
|
|
|
Powered by
FUDForum. Page generated in 0.42091 seconds