From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19385 invoked by alias); 28 Feb 2007 19:36:00 -0000 Received: (qmail 19359 invoked by uid 22791); 28 Feb 2007 19:35:59 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 28 Feb 2007 19:35:49 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id 295CF48CF90 for ; Wed, 28 Feb 2007 14:35:45 -0500 (EST) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 14528-01-10 for ; Wed, 28 Feb 2007 14:35:45 -0500 (EST) Received: from takamaka.act-europe.fr (unknown [70.71.0.212]) by nile.gnat.com (Postfix) with ESMTP id B5F2548CEE6 for ; Wed, 28 Feb 2007 14:35:44 -0500 (EST) Received: by takamaka.act-europe.fr (Postfix, from userid 1000) id 860D3E7972; Wed, 28 Feb 2007 11:35:51 -0800 (PST) Date: Wed, 28 Feb 2007 19:36:00 -0000 From: Joel Brobecker To: gdb-patches@sourceware.org Subject: Re: [RFA] Fix typo in replace type Message-ID: <20070228193551.GG13140@adacore.com> References: <20070228192410.GM28322@adacore.com> <20070228193056.GA13684@caradoc.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070228193056.GA13684@caradoc.them.org> User-Agent: Mutt/1.4.2.2i 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: 2007-02/txt/msg00386.txt.bz2 > On Wed, Feb 28, 2007 at 11:24:10AM -0800, Joel Brobecker wrote: > > 2007-02-28 Joel Brobecker > > > > * gdbtypes.c (replace_type): Fix typo that caused us to not update > > length of the types referenced by the new type CV ring. > > > > Tested on x86-linux, no regression. OK to apply? > > OK. Thanks, will commit momentarily. > Do you mean this completely fixed the issue? Not completely, no, we still need to add handling for the anonymous forward reference, but I decided that this separate issue deserved a separate commit... Thanks, -- Joel