Date: Mon, 3 Mar 1997 06:17:48 -0800 (PST) From: pir@pir.net To: freebsd-gnats-submit@freebsd.org Subject: bin/2856: "sh -c 'emacs-nw'" then ctrl-g crashes sh Message-ID: <199703031417.GAA02197@freefall.freebsd.org> Resent-Message-ID: <199703031420.GAA02391@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 2856 >Category: bin >Synopsis: "sh -c 'emacs-nw'" then ctrl-g crashes sh >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Mar 3 06:20:00 PST 1997 >Last-Modified: >Originator: Peter Radcliffe >Organization: pir >Release: 2.1.5-RELEASE >Environment: FreeBSD moek 2.1.5-RELEASE FreeBSD 2.1.5-RELEASE #0: Sat Mar 1 15:09:54 GMT 1997 pir@moek:/usr/src/sys/compile/MOEK i386 >Description: I've tested this with sh from -current and emacs 19.34.1 If you run sh -c 'emacs -nw' and then press control-g (at any stage in editing) it appears that sh crashes, leaving emacs looping on an error trying to access it's tty. tcsh or bash -c 'emacs -nw' does not exibit this problem. ktrace sh -c 'emacs -nw' gives: [...] 22003 sh NAMI "/usr/local/bin/emacs" 22003 sh RET stat 0 22003 sh CALL break(0x55ffc) 22003 sh RET break 0 22003 sh CALL break(0x56ffc) 22003 sh RET break 0 22003 sh CALL fork 22003 sh RET fork 22004/0x55f4 22003 sh CALL getpgrp 22003 sh RET getpgrp 22003/0x55f3 22003 sh CALL wait4(0xffffffff,0xefbfd5d4,0x2,0) 22003 sh PSIG SIGINT SIG_DFL Messy signal handling somewhere ? >How-To-Repeat: sh -c 'emacs -nw' Press control-g >Fix: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703031417.GAA02197>