[GATTACA]

Hello.

I'm using a Powerbook 800Mhz G4 with Jaguar. I'm using the terminal emulator called 'GLTerm' to interface with the Unix component of OS X. I applied the recent security patches that 'Update' found. Now when I use GLTerm I can't kill an operation. For instance if I'm debugging a script and it enters an infinite loop, I use to be able to hit CTRL-C and kill it. Now when I do this I get ^C printed to the screen but the script continues to execute.

The only change has been the security updates.

Using the built in 'Terminal' application works fine, but I like the rendering done by GLTerm.

Has anyone else encountered this problem?

[johnMG]

Did you try cmd-.
?

[[APi]TheMan]

Check your terminal line settings... use stty --all to see what your settings are:

Code:
[aorth@Alan-Orths-Computer: ~]$ stty --all
speed 9600 baud; rows 24; columns 80;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; start = ^Q; stop = ^S; susp = ^Z; dsusp = ^Y; rprnt = ^R;
werase = ^W; lnext = ^V; flush = ^O; status = <undef>; min = 1; time = 0;
-parenb -parodd cs8 hupcl -cstopb cread -clocal -crtscts
-ignbrk brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff
ixany imaxbel
opost onlcr
isig icanon iexten echo echoe -echok -echonl -noflsh -tostop -echoprt echoctl
echoke

The important part being the ^C for "interrupt". If interrupt is set to something different, or not set at all, set it back to ^C by typing: stty intr ^C

The "^" means "control", just in case you hadn't picked that up through using the Terminal yet. I hope that fixes it.

[GATTACA]

No good. Here's what I get for 'stty -a':

speed 9600 baud;
lflags: echoe echoke echoctl pendin
oflags: -oxtabs
cflags: cs8 -parenb
[dfermin@gandalf: dfermin]$ stty -a
speed 9600 baud; 48 rows; 80 columns;
lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl
-echoprt -altwerase -noflsh -tostop -flusho pendin -nokerninfo
-extproc
iflags: -istrip icrnl -inlcr -igncr ixon -ixoff ixany imaxbel -ignbrk
brkint -inpck -ignpar -parmrk
oflags: opost onlcr -oxtabs
cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -mdmbuf
cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = <undef>;
eol2 = <undef>; erase = ^?; intr = ^C; kill = ^U; lnext = ^V;
min = 1; quit = ^\; reprint = ^R; start = ^Q; status = <undef>;
stop = ^S; susp = ^Z; time = 0; werase = ^W;

I can see that 'intr' is set to '^C' I reset it just in case but that didn't do anything.
I tried 'cmd-.' but that didn't work either.

Could this problem be a side effect of configuring CPAN? I now realize I configured CPAN the same day I installed the security updates.

[[APi]TheMan]

Originally posted by GATTACA:
No good. Here's what I get for 'stty -a':

speed 9600 baud;
lflags: echoe echoke echoctl pendin
oflags: -oxtabs
cflags: cs8 -parenb
[dfermin@gandalf: dfermin]$ stty -a
speed 9600 baud; 48 rows; 80 columns;
lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl
-echoprt -altwerase -noflsh -tostop -flusho pendin -nokerninfo
-extproc
iflags: -istrip icrnl -inlcr -igncr ixon -ixoff ixany imaxbel -ignbrk
brkint -inpck -ignpar -parmrk
oflags: opost onlcr -oxtabs
cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -mdmbuf
cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = <undef>;
eol2 = <undef>; erase = ^?; intr = ^C; kill = ^U; lnext = ^V;
min = 1; quit = ^\; reprint = ^R; start = ^Q; status = <undef>;
stop = ^S; susp = ^Z; time = 0; werase = ^W;

I can see that 'intr' is set to '^C' I reset it just in case but that didn't do anything.
I tried 'cmd-.' but that didn't work either.

Could this problem be a side effect of configuring CPAN? I now realize I configured CPAN the same day I installed the security updates.

Yikes. I'm not sure. E-mail the developer?