Tcl interpreter run by Tkinter quits ! Any clue ?

[David Konerding]

On Mon, 28 May 2001 10:26:05 -0700, Michel Sanner <sanner at scripps.edu> wrote:
> Hello,
> 
> I started working on a Python-Tkinter based vusial programing environment
> and I am running into the following problem:
> 
> The whole application quits and I get the following message:
> 
> TclExecuteByteCode: done instruction at pc 4: stack top 0 != entry stack
> top-1
>   Source: "11291968callit"TclExecuteByteCode execution failure: end stack
> top != start stack top
> 
> The application is fairly complex, using threading for events queuing,
> data flow and execution of computational nodes.
> 
> It is not happening every time :( which makes it hard to debug !
> 
> If anyone has (even just a beggining of) a clue I would appreciate it very
> much.
> 
> Thanks

Hi Michel,


I believe the problem is due to Tcl being not thread-safe.  You basically can use
Tkinter drectly only in one thread-- I believe it's OK if it's not the main thread.

Dave