Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
To: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: subprocs in Emacs shells won't die with comint-interrupt-subjob
References: <002c01bfec7c$1385d120$1d0ea8c0 AT visi DOT com>
From: dkarr AT tcsi DOT com (David M. Karr)
Date: 13 Jul 2000 08:00:27 -0700
In-Reply-To: "Jeff Jensen"'s message of "Wed, 12 Jul 2000 22:40:18 -0500"
Message-ID: <uysnte9it0.fsf@tcsi.com>
Lines: 33
X-Mailer: Gnus v5.5/Emacs 20.6

>>>>> "Jeff" == Jeff Jensen <jeffjensen AT nospam DOT visi DOT com> writes:
  Jeff> I also have the same issue most of the time.  I resort to using the Kill
  Jeff> option on the Signals menu and it always works.  I may try the Quit option
  Jeff> first and occasionally it works too (C-c C-\).

  Jeff> -----Original Message-----
  Jeff> From: cygwin-owner AT sources DOT redhat DOT com
  Jeff> To: cygwin AT sourceware DOT cygnus DOT com
  Jeff> Subject: subprocs in Emacs shells won't die with comint-interrupt-subjob

  Jeff> With the new Cygwin, when I run a subprocess in an Emacs shell,
  Jeff> pressing C-c C-c (which executes "comint-interrupt-subjob") does not
  Jeff> kill the subprocess.  The title bar flashes, but that's all.  When the
  Jeff> running process is a Java application, it also does a thread dump,
  Jeff> which is supposed to happen when it gets a "QUIT" signal.  I've
  Jeff> verified these symptoms with Emacs v 20.4, 20.6, and 20.7.

  Jeff> However, if I retreat to Cygwin B20.1, without changing anything else,
  Jeff> this symptom goes away.  Pressing C-c C-c in the shell properly kills
  Jeff> the subprocess.

  Jeff> I'd really like to move up to the new cygwin, but not being able to
  Jeff> easily kill subprocesses in the shell is extremely inconvenient.

So it appears that with the old cygwin, it is sending the correct
"interrupt" signal, but with the new cygwin, it is sending the "quit"
signal.  Does anyone know why this might be happening?  Is anyone
addressing this issue?

-- 
===============================================================================
David M. Karr     ; dkarr AT tcsi DOT com  ; w:(425)487-8312 ; TCSI & Best Consulting
Software Engineer ; Unix/Java/C++/X ; BrainBench CJ12P (6/12/2000)


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com