There seem to be no tools to detect or deal with threads stalled by
synchronization errors,
and If I do decide (by monitoring the lack of activity for example) that a
thread is stalled,
there is precious little I can do about it.
Thread.interrupt() seems to do nothing at all.
Looking at CodenameOneThread, it superficially looks like a method
like
public static void storeStack(Thread t,Throwable th)
> {
> CodenameOneThread c = (CodenameOneThread)t;
> c.storeStackForException(th, c.stackPointer);
> }
>
>
would allow capture of a stack trace, but c.stackPointer seems to not be
maintained
for the non-current thread.
although what would be really useful would be to know what thread holds the
monitor
that the stalled thread is waiting for. I appreciate that there may be
underlying difficulties
doing this kind of thing on all the platforms, but at least it ought to be
possible in the
simulator.
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
Visit this group at https://groups.google.com/group/codenameone-discussions.
To view this discussion on the web visit
https://groups.google.com/d/msgid/codenameone-discussions/16c8472c-795e-4b25-82c2-b8317774518a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
