From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21003 invoked by alias); 6 Oct 2011 21:00:18 -0000 Received: (qmail 20979 invoked by uid 22791); 6 Oct 2011 21:00:16 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 06 Oct 2011 21:00:01 +0000 Received: from nat-ies.mentorg.com ([192.94.31.2] helo=EU1-MAIL.mgc.mentorg.com) by relay1.mentorg.com with esmtp id 1RBv2t-0003Lv-Nc from pedro_alves@mentor.com ; Thu, 06 Oct 2011 13:59:59 -0700 Received: from scottsdale.localnet ([172.16.63.104]) by EU1-MAIL.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 6 Oct 2011 21:59:57 +0100 From: Pedro Alves To: Joel Brobecker Subject: Re: [RFA/RFC] Restore old handling of multi-register variables Date: Thu, 06 Oct 2011 21:00:00 -0000 User-Agent: KMail/1.13.6 (Linux/2.6.38-11-generic; KDE/4.7.1; x86_64; ; ) Cc: gdb-patches@sourceware.org References: <1317675787-7351-1-git-send-email-brobecker@adacore.com> <201110061854.52856.pedro@codesourcery.com> <20111006201053.GS19246@adacore.com> In-Reply-To: <20111006201053.GS19246@adacore.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201110062159.55379.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: 2011-10/txt/msg00183.txt.bz2 On Thursday 06 October 2011 21:10:53, Joel Brobecker wrote: > > This is a bit a step backwards in that it doesn't allow > > marking parts of the value as unavailable when the type > > is longer than one register. get_frame_register_value > > was invented to allow for partially available registers. > > I understand. > > The bummer part is that I'm entering my busiest time of the year, > and I haven't followed all this close enough to whip up a quick fix. > So I'll keep that on my list to look at. Note that AVR will > have to remain completely broken. We'll just have to add a note > if we release 7.4 with that problem. Well, your patch doesn't really make it worse, so I won't object if you want to put it in. It's not perfect, but it's better than what we have now, which doesn't work even for fully available values. -- Pedro Alves