Good catch - that definitely looks wrong and I'll make the fix.
I'll put a more generic log message outside the catch statement because
I still want something logged in this case.
- Don
Michael Williams wrote:
> I think I found one source of CGOS lockups. In
> cgos.vfs/lib/app-cgos/cgos.tcl, the following code exists:
>
> proc send {sock msg} {
> if { [catch { puts $sock $msg }] } {
> set who $id($sock)
> log "alert: Socket crash for user: $who"
> }
> }
>
> But when the third line down fails, cgos goes into some weird state.
> That line and the next are non-essential and can ignore errors. So it
> can be fixed like this:
>
> proc send {sock msg} {
> if { [catch { puts $sock $msg }] } {
> catch {
> set who $id($sock)
> log "alert: Socket crash for user: $who"
> }
> }
> }
> _______________________________________________
> computer-go mailing list
> [email protected]
> http://www.computer-go.org/mailman/listinfo/computer-go/
>
_______________________________________________
computer-go mailing list
[email protected]
http://www.computer-go.org/mailman/listinfo/computer-go/
