Date: Wed, 9 Oct 1996 10:38:03 -0400 (EDT)
From: Christopher Masto <exidor@superior.net>
To: FreeBSD-gnats-submit@freebsd.org
Subject: kern/1751: system("emacs") shows signal handling problem
Message-ID: <199610091438.KAA26945@nimbus.superior.net>
Resent-Message-ID: <199610091440.HAA28202@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 1751
>Category: kern
>Synopsis: system() call appears to be broken re: signal handling
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Wed Oct 9 07:40:01 PDT 1996
>Last-Modified:
>Originator: Christopher Masto
>Organization:
Superior Net
>Release: FreeBSD 2.1.0-RELEASE i386
>Environment:
Any environment.
>Description:
Several programs which spawn an editor (trn, elm, etc.) seemed to have
a problem when using emacs as the editor. Pressing C-g (abort) in
emacs caused the program to re-take control of the tty, with emacs
still running but unusable. This problem was also mentioned in
bin/1206 as a bug in '/bin/sh -c emacs'. It turns out that it isn't
/bin/sh at all, but in fact anything that uses the system() call.
>How-To-Repeat:
Compile and run the following:
main()
{ system("emacs -nw") }
When emacs starts, press C-g. It will dump you back to the shell, usually
with the terminal modes screwed up, and emacs will still show up in a 'ps'.
(And it will occasionally write "garbage collecting" to the terminal)
>Fix:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610091438.KAA26945>