Hi All,

It turns out that I misread the stackchecking code (oops, brown paper bag
time), and that it is not at fault.


The problem is that Tcl has a thread model where one can have multiple
interpreters per thread, but may not call an interpreter from another thread
then the one it was created in, and this is just what 8Kingdoms was doing.


I'm working on a fix. In the mean time please turn stackchecking in the TCL
packages back on, it was not at fault and acutally caught an error. 8Kingdoms
working without it was more luck then anything else.


Thanks & Regards,

Hans

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

On Tue, 2008-01-08 at 10:28 +0100, Hans de Goede wrote:
> 8Kingdoms working without it was more luck then anything else.

I'd say it was more a failure on the part of the TCL devs to do proper
checking, but water under the bridge.

--
Ignacio Vazquez-Abrams <ivazqueznet@gmail.com>

PLEASE don't CC me; I'm already subscribed
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Ok, I rebuilt it with stack checking.

Ignacio Vazquez-Abrams wrote:

On Tue, 2008-01-08 at 10:28 +0100, Hans de Goede wrote:


8Kingdoms working without it was more luck then anything else.



I'd say it was more a failure on the part of the TCL devs to do proper
checking, but water under the bridge.




--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list