when Task.run() throws uncaught exception RequestProcessor should print
the stack trace at the point when a Task is enqueued, it helps identify the
faulty Task.

Following is email communications between trung and jarda

-------------------------
From: Jaroslav Tulach <jaroslav.tulach@netbeans.com>
Subject: RE: req processor - debug suggestion
To: Trung Duc Tran <trung.duc.tran@netbeans.com>

Date: Mon, 17 Apr 2000 11:22:53 +0200

Vcelku souhlasim. Akorat znam lepsi zpusob, jak to psat.

add (Task t)
  e = new Exception ();
}


a nekdy pozdeji se udela

e.pst ();

Pak uz ani nemusi byt nastaven nejaky specialni flag. Prosim, prosim,
strc mi to do ST.
Jarda

> -----Original Message-----
> From: Trung Duc Tran [mailto:trung.duc.tran@netbeans.com]
> Sent: Monday, April 17, 2000 11:13 AM
> To: jaroslav.tulach@netbeans.com
> Subject: req processor - debug suggestion
>

>
> Jardo,
>
> zrovna mam tohle
>
> ,----
> | Exception occurred in request processor:
> | java.lang.NullPointerException
> |         at
> org.openide.loaders.InstanceDataObject$InstanceNode.run(Instan
> ceDataObject.java, Compiled Code)
> |         at org.openide.util.Task.run(Task.java, Compiled Code)
> |         at
> org.openide.util.RequestProcessor$ProcessorThread.run(RequestP
> rocessor.java, Compiled Code)
> `----
>
> Myslim si, ze by bylo dobre, aby RequestProcessor v tom pripade
> hazel take stack trace v tom okamziku kdy ten Task byl dan do
> fronty.  Takhle sice vim, ze se exception stal v InstanceDataObject
> ale je to trochu malo.  Neco takovyhohle (pseudo-code)
>
> add(Task t) {

>     Thread.dumStack(byteArrayStream);
>     ....
> }
>
> Samozrejme, ze se to ma delat jenom kdyz je definovan nejaky system
> property
>
> Co ty na to?
>