From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22160 invoked by alias); 1 Dec 2008 21:22:10 -0000 Received: (qmail 22152 invoked by uid 22791); 1 Dec 2008 21:22:09 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 01 Dec 2008 21:21:32 +0000 Received: (qmail 27281 invoked from network); 1 Dec 2008 21:21:30 -0000 Received: from unknown (HELO orlando.local) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 1 Dec 2008 21:21:30 -0000 From: Pedro Alves To: gdb-patches@sourceware.org Subject: Re: [RFA] dummy frame handling cleanup, plus inferior fun call signal handling improvement Date: Mon, 01 Dec 2008 21:22:00 -0000 User-Agent: KMail/1.9.10 Cc: Doug Evans References: <20081118125838.0613C412301@localhost> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200812012121.59580.pedro@codesourcery.com> 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-12/txt/msg00015.txt.bz2 Hi Doug, I'd like to bring a current GDB deficiency to your attention, in case it affects anything related to this patch. If GDB stops due to a signal instead of hitting the dummy frame breakpoint, and you have set GDB to restore the state automatically with "set unwindonsignal on", and the thread that reported the signal (say a SIGSEGV) was *not* the same that was doing the infcall, GDB will currently restore the old context to the wrong thread (seen by inspection, having really tried it). Not having studied the patch yet, I'm just wondering if your changes would make it easier or harder to fix this, or if you could be extending the problem by possibly restoring things in the wrong thread as well. -- Pedro Alves