#1227 control-break does not stop tclsh82

[Anonymous]

OriginalBugID: 2619 Bug
Version: 8.2.3
SubmitDate: '1999-08-31'
LastModified: '2000-02-08'
Severity: SER
Status: Assigned
Submitter: techsupp
ChangedBy: hobbs
RelatedBugIDs: 4132
OS: Windows 98
Machine: X86
FixedDate: '2000-10-25'
ClosedDate: '2000-10-25'

Name: Harold M. Kaplan

ReproducibleScript:
set port 25
proc bgerror {trouble} {puts stdout "bgerror: $trouble"}
proc answer {socketChannel host2 port2} {}
socket -server answer $port
vwait forEver

ObservedBehavior:
If the script is started with tclsh82, there is no easy way to stop it.
Control-break does not work on it. I still have my old
copy of tclsh80, and control-break stops it just fine. I am speaking of
tclsh; wish gives no trouble at all, since the mouse
can stop it.

DesiredBehavior:
I expect control-break to stop tclsh82 as it stops tclsh80.

Ctrl-break works as expected (killing off tclsh82) for WinNT.
Must be checked on Win9*.
-- 10/19/1999 hobbs
Doesn't work as expected for Win98.
-- 11/10/1999 hobbs

[David Gravereaux]

Actually, tclsh (or tclAppInit.c) doesn't contain a ConsoleCtrHandler for intecepting this notice. Similar to signals on unix. See bug 119355 for a proposal of such a thing.

[Don Porter]

Logged In: YES
user_id=80530

I don't have a Win98 machine to work on this.
Assigning to the owner of the proposed fix
in 219355.

[David Gravereaux]

Logged In: YES
user_id=7549

no time to do this.

[Don Porter]

Logged In: YES
user_id=80530

Rumor has it WIndows 98 has
reached it's end of life, so I'm
closing this Won't Fix pending
any cries of outrage.