From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5161 invoked by alias); 17 Sep 2011 19:06:51 -0000 Received: (qmail 5152 invoked by uid 22791); 17 Sep 2011 19:06:50 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 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; Sat, 17 Sep 2011 19:06:36 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 22F7C2BB1D0; Sat, 17 Sep 2011 15:06:36 -0400 (EDT) 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 K+cGPzJWCdsM; Sat, 17 Sep 2011 15:06:36 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id ECA742BB1CC; Sat, 17 Sep 2011 15:06:35 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id CF917145615; Sat, 17 Sep 2011 15:06:24 -0400 (EDT) Date: Sat, 17 Sep 2011 19:06:00 -0000 From: Joel Brobecker To: Alexander Petukhov Cc: gdb@sourceware.org Subject: Re: proper usage of "-exec-interrupt" Message-ID: <20110917190624.GQ12670@adacore.com> References: <4E7449BD.4030405@apetukhov.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E7449BD.4030405@apetukhov.ru> 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-09/txt/msg00062.txt.bz2 > Whay does this signal come to parent process and can I avoid this > somehow? This is a bit of a guess, since I don't remember all the details, but I think it might be a question of process group. To implement the interrupt, many targets simply send a SIGINT signal to the inferior process group. If you spawned GDB within the same process group as GDB, and both GDB and the program being debugged share the same process group as well, the interrupt will cause SIGINT to be received by your IDE as well. So, try spawning GDB in its own process group. -- Joel