| allenjo5@mail.northgrum.com 2006-12-15, 7:10 pm |
|
allenjo5@mail.northgrum.com wrote:
> Both tcl and tk were built with --enable-threads. Tcl passed all but
> two minor tests: clock-10.0 and clock-41.1, which are strftime format
> tests. Tk failed many of the font tests, which I think I can live
> with, but the windows-2.9 hang troubles me. The code is this:
>
> test window-2.9 {Tk_DestroyWindow, Destroy bindings evaluated after
> exit} \
> unixOrWin {
> set script [makeFile {
> toplevel .t1
> toplevel .t2
> update
> bind .t2 <Destroy> {puts "Destroy .t2" ; exit 1}
> bind .t1 <Destroy> {puts "Destroy .t1" ; exit 0}
> destroy .t2
> } script]
> set error [catch {exec [interpreter] $script -geometry 10x10+0+0}
> msg]
> removeFile script
> list $error $msg
> } {0 {Destroy .t2
> Destroy .t1}}
>
> Testing it without the test wrappings, I find that this hangs:
>
> toplevel .t1
> toplevel .t2
> update
> bind .t1 <Destroy> {puts "Destroy .t1" ; exit 0}
> destroy .t2
>
> But when I remove the "exit 0" it doesn't:
>
> toplevel .t1
> toplevel .t2
> update
> bind .t1 <Destroy> {puts "Destroy .t1" ; }
> destroy .t2
>
> How serious is this, and what might I do to fix it?
Well, I figured out how to make the windows-2.9 test _not_ hang: build
tcl and tk without threads enabled (the default). I had been using the
--enable-threads configure option. I should have known that threads
were trouble, especially on AIX :-( But I'd still like to know what
the exact problem is. It seems a shame not to build with threads just
because one measly test hung.
John.
Hope
|