From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10417 invoked by alias); 7 Dec 2011 09:53:35 -0000 Received: (qmail 10406 invoked by uid 22791); 7 Dec 2011 09:53:34 -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; Wed, 07 Dec 2011 09:53:21 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id C94DD2BB26D; Wed, 7 Dec 2011 04:53:17 -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 SGJIj+N3wE5Y; Wed, 7 Dec 2011 04:53:17 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 3AB012BB050; Wed, 7 Dec 2011 04:53:16 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id D8F96145615; Wed, 7 Dec 2011 01:53:13 -0800 (PST) Date: Wed, 07 Dec 2011 09:54:00 -0000 From: Joel Brobecker To: Hui Zhu , Stan Shebs , yao@codesourcery.com Cc: gdb-patches@sourceware.org Subject: Re: creating the gdb-7.4 branch tomorrow (?) Message-ID: <20111207095313.GA21915@adacore.com> References: <20111205081911.GG28486@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-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: 2011-12/txt/msg00223.txt.bz2 Stan, Yao, > I found a issue http://sourceware.org/ml/gdb-patches/2011-12/msg00177.html > And I think it is really affect tracepoint function(Second tstart will > reproduce it). [assuming that we can't get this problem fixed today] You seem to be the ones having made the most modifications to tracepoint.c. Can you help us evaluate whether the fix is likely to be considered "risky"? If you think the fix is going to be relatively simple, then we can go ahead with the branch, and fix the problem on the branch. If not, then we have to wait before we branch, and that means opening the door for other problems to creep in. Thanks, -- Joel