It actually isn't as daunting as it sounds because we could assume
that there's a single thread in the thread-pool.
On 02/25/2011 08:35 AM, Pawel Piech wrote:
Hi Abeer,
This is an old bug (236915) and it's entirely fixable, it just
needs a a brave soul to re-implement the
java.util.concurrent.ScheduledExecutorService without violating
any copy rights :-)
Cheers,
Pawel
On 02/25/2011 02:58 AM, Abeer Bagul wrote:
Hi All,
I create a subclass of DsfRunnable (say MyRunnable). In the
run() method, there is some code which throws a
NullPointerException (or any other runtime exception). I submit
this runnable using DefaultDsfExecutor.execute().
Now the client has submitted the runnable in a worker thread,
and the NPE occurs in the DSF thread. In this case, the call
stack is not printed to the console, and there is no indication
of an exception having been thrown. The only indication is the
DSF executor thread remains stuck in the exception handler and
further runnables are not processed.
Can the default handling of exceptions be changed so that
atleast the stacktrace is printed to the console when a runtime
exception occurs in the runnable?
Thanks
Abeer Bagul
Tensilica India
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
|
