I did not have any knowledge about those fixes (even after 45 min speak
with Serge), so thanks for the tip.
It seems ok for me. Can you check it back ?
> b. What is the reason for overriding what parse has set in the interruptible
The reason is after having an error in syncexec, the storecommand is put
in uninterruptible mode.
So all the callbacks we were storing after that were looping endlessly.
You can reproduce that behaviour with those steps :
- open scipad
- type "error(10)"
all seems allright...
- close scipad
- do 1+2 in the console, you lost scilab.
He is looping on an empty command that can not end because it's
I am a bit busy for now, I promiss to write some documentation about the
new Tcl behaviour.
To put it shortly, we have now a separated thread for Tcl stuff.
And those commands were making reentrant call so that we stay in a
I guess it is the same issue with debug mode.
> 3. Still in scilabexec.tcl:
> ScilabEval_lt "flush"
> must be useless since all the previous ScilabEvals use "sync" "seq".
> If your changes do no longer work when you remove the flush, then it means that
> the sync option of ScilabEval does not work.
Oups... My mistake...
It was only a debug/investigation purpose.
It works fine for me without this. Is it ok for you too ?
___SCILAB - INRIA Rocquencourt___
Domaine de Voluceau - B.P. 105
78153 Le Chesnay Cedex
Tel : (+33/0)188.8.131.52.63
Mailto : [hidden email] http://www.scilab.org
Bruno JOFRET said on 07/03/2008 17:30:
> It seems ok for me. Can you check it back ?
I tried with the most up-to-date Scilab svn. It's OK for me (on Windows).
> I am a bit busy for now, I promiss to write some documentation about the
> new Tcl behaviour.
OK, noted ;-)
> To put it shortly, we have now a separated thread for Tcl stuff.
> And those commands were making reentrant call so that we stay in a
> deadlock process.
Not sure I understand you here, but you said you would detail this
later, which is fine for me.
> I guess it is the same issue with debug mode.
>> 3. Still in scilabexec.tcl:
>> ScilabEval_lt "flush"
> Oups... My mistake...
> It was only a debug/investigation purpose.
> It works fine for me without this. Is it ok for you too ?
It must work without it anyway.
Good luck for the upcoming changes in the Tcl loop. I have already
seen misc. improvements in the recent past, for instance there is no
need for me to hit enter in the shell any longer to make the event
loop move. This can be seen for instance when "Open source of...", or
when Ctrl-F& inside a word in Scipad. However the debugger is still
completely broken. Let me know if I can be of any help on this topic.