Re: [clif] console gui instability

[Bruno Dillenseger <bruno.dillenseger@xxxxxxxxxxxxxxxxxxxx>]

You should have jdb included in your JDK. I only tried the server mode 
(you connect jdb to a running JVM with ad hoc properties).
I currently use Idea's debugger, but Idea is not free. Eclipse does have 
a debugger also.

Since your GUI freezes, I need to know on which call the GUI's AWT event 
thread is blocked (the stack trace of this thread). To get this, you run 
the console in the debugger, and when the GUI is frozen, you suspend the 
AWT-event thread, you look at its stack (and possibly the involved 
objects), and you copy/paste/send it.

Hope it helps,
-- Bruno.

olivier gusching a écrit:

> Thanks for your answer,
>
> Could you give me more information, and/or an advice for a specific 
> debug tool to see where the problem comes from ?
>
> regards,
>
> Olivier
>
> Bruno Dillenseger wrote:
>
> > olivier gusching a écrit:
> >
> > > Did you have the time to have a look at my console GUI instability 
> > > issue ? 
> >
> >
> > Yes and no.
> > I solved a similar problem on the new version I'm currently preparing 
> > but which is not in the CVS yet. However, the architecture with 
> > regard to the console/supervision part has been redesigned, and the 
> > fix do not apply to the old code. Moreover, I never had this freeze 
> > during scenario execution (I only experienced freeze with the new 
> > unreleased version, and always before reaching deployment step), and 
> > I have no stack trace of your problem.
> >
> > So, now, there are 2 solutions:
> >
> >     * either you try to run with a debugger so as to give me the stack
> >       trace of the AWT-event thread (to see on which call it is blocked)
> >     * or you go on until the release of the new version (hopefully by
> >       the end of this month)