From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27148 invoked by alias); 2 Mar 2011 15:04:23 -0000 Received: (qmail 27139 invoked by uid 22791); 2 Mar 2011 15:04:22 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,TW_QE X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 02 Mar 2011 15:04:18 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id D062C2BB00E; Wed, 2 Mar 2011 10:04:16 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id tw1fssIB7zBg; Wed, 2 Mar 2011 10:04:16 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 1FBA02BAE0C; Wed, 2 Mar 2011 10:04:16 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id A881B1459AD; Wed, 2 Mar 2011 19:03:59 +0400 (RET) Date: Wed, 02 Mar 2011 15:04:00 -0000 From: Joel Brobecker To: "dpc@ucore.info" Cc: Tristan Gingold , Pedro Alves , gdb@sourceware.org, Mike Frysinger Subject: Re: gdb + remote qemu, Ctrl-C does not work Message-ID: <20110302150359.GB2513@adacore.com> References: <201103020945.11471.pedro@codesourcery.com> <201103021249.34558.pedro@codesourcery.com> <0EA5A1E3-9098-457F-9334-74476345C908@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-03/txt/msg00020.txt.bz2 > > Usually background processes don't get C-c. > > I am not sure, but I'd guess so. But what Pedro Alves says would > explained everything perfectly. That's only the case with interactive shells! In non-interactive shell sessions (typically a script), background process are still launched with the same process group as the parent script. Since the SIGINT is propagated to all processes sharing the foreground process group ID, this should explain why qemu is receiving the SIGINT as well. -- Joel