From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23398 invoked by alias); 28 Aug 2008 22:33:16 -0000 Received: (qmail 23388 invoked by uid 22791); 28 Aug 2008 22:33:15 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 28 Aug 2008 22:32:36 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 3518498189; Thu, 28 Aug 2008 22:32:34 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 0D9CB98187; Thu, 28 Aug 2008 22:32:33 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1KYq2a-0001kj-VS; Thu, 28 Aug 2008 18:32:32 -0400 Date: Thu, 28 Aug 2008 22:33:00 -0000 From: Daniel Jacobowitz To: Michael Snyder Cc: gdb-patches@sourceware.org Subject: Re: RFC: Do not call write_pc for "signal SIGINT" Message-ID: <20080828223232.GA6407@caradoc.them.org> Mail-Followup-To: Michael Snyder , gdb-patches@sourceware.org References: <20080828155520.GA23110@caradoc.them.org> <48B6E9F4.5080403@vmware.com> <20080828181841.GA30866@caradoc.them.org> <48B6EFBD.2090203@vmware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48B6EFBD.2090203@vmware.com> User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-08/txt/msg00656.txt.bz2 On Thu, Aug 28, 2008 at 11:34:37AM -0700, Michael Snyder wrote: > More than a testcase. This isn't very well explained. > You didn't reference the PR in your original post, and It was in the ChangeLog entry, sorry. > I'm still not sure how we're getting from SIGINT to > signal 0... We aren't. The comment that I'm deleting is talking about the user typing "signal 0", which worked correctly; I'm making "signal SIGINT" treat the PC the same way. All the complexity is in incorrect bits I'm deleting :-) Afterwards it's like every other call to proceed in the file. -- Daniel Jacobowitz CodeSourcery