Sounds like stack corruption. Just guessing here. But I don't trust
QuickTimeTcl on 8.5 since I access an internal struct MacDrawable assuming
there is a member Region visRgn or something when it now is a HIShape. It
could be anything but it's good to have the stack trace at least. If it is
stack corruption it doesn't help, though. I was thinking of installing the
latest ejabberd and write a script that registers 1000 users and keeps 100
of them online. That would be a stress test. I can run Tcl/Tk in the Xcode
debugger with al kinds of memory checks on. That should crash at the right
(wrong) place.
Sounds like stack corruption. Just guessing here. But I don't trust
QuickTimeTcl on 8.5 since I access an internal struct MacDrawable assuming
there is a member Region visRgn or something when it now is a HIShape. It
could be anything but it's good to have the stack trace at least. If it is
stack corruption it doesn't help, though. I was thinking of installing the
latest ejabberd and write a script that registers 1000 users and keeps 100
of them online. That would be a stress test. I can run Tcl/Tk in the Xcode
debugger with al kinds of memory checks on. That should crash at the right
(wrong) place.