From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21151 invoked by alias); 17 May 2010 12:57:04 -0000 Received: (qmail 21140 invoked by uid 22791); 17 May 2010 12:57:03 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 17 May 2010 12:56:59 +0000 Received: (qmail 10942 invoked from network); 17 May 2010 12:56:57 -0000 Received: from unknown (HELO localhost) (froydnj@127.0.0.2) by mail.codesourcery.com with ESMTPA; 17 May 2010 12:56:57 -0000 Date: Mon, 17 May 2010 13:20:00 -0000 From: Nathan Froyd To: Michael Snyder Cc: "gdb-patches@sourceware.org" Subject: Re: [RFC] persistence of schedlock mode Message-ID: <20100517125656.GN5834@codesourcery.com> References: <4BEAEEB0.5040202@vmware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BEAEEB0.5040202@vmware.com> User-Agent: Mutt/1.5.17+20080114 (2008-01-14) 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: 2010-05/txt/msg00342.txt.bz2 On Wed, May 12, 2010 at 11:08:48AM -0700, Michael Snyder wrote: > I don't think this is a problem for mode "step", and it could > be argued that mode "on" is "use at your own risk". However > I've been thinking about how to resolve it, and this simple > but intrusive patch is what I come up with. You should add a declaration for reset_schedlock someplace; otherwise, you get: gdb/target.c: In function 'target_mourn_inferior': gdb/target.c:2249: error: implicit declaration of function 'reset_schedlock' -Nathan