From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19684 invoked by alias); 9 Jun 2003 00:22:19 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 19615 invoked from network); 9 Jun 2003 00:22:16 -0000 Received: from unknown (HELO localhost.redhat.com) (24.157.166.107) by sources.redhat.com with SMTP; 9 Jun 2003 00:22:16 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 076F52B63; Sun, 8 Jun 2003 20:22:15 -0400 (EDT) Message-ID: <3EE3D336.1080108@redhat.com> Date: Mon, 09 Jun 2003 00:22:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Kettenis Cc: gdb-patches@sources.redhat.com Subject: Re: [cagney_convert-20030606-branch] Add value to REGISTER_TO_VALUE et.al. References: <3EDE4A9E.70403@redhat.com> <8665nl34ao.fsf@elgar.kettenis.dyndns.org> <3EE0D987.6030207@redhat.com> <200306081643.h58GhiTr048427@elgar.kettenis.dyndns.org> <3EE36F28.9000104@redhat.com> <3EE3B455.7080902@redhat.com> <200306082250.h58Mow31022350@elgar.kettenis.dyndns.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-06/txt/msg00290.txt.bz2 > And what do these functions do if the register is unavailable in a > certain frame? That shouldn't happen if we have complete debug > information, but unfortunately we almost certainly don't have that. > Should this be reported to the user or not? Should we set > VALUE_OPTIMIZED_OUT, just as we do for registers that don't need > conversion? If so, we probably need a return value that indicates > whether the conversion was successfull. I've got into the habit of ignoring OPTIMIZED_OUT, for registers it's always cleared (well ignoring the recent CFI stuff). It was added between 3.5 and 3.93 but for no apparent reason (at least for registers). The ChangeLog's are not very enlightenting and this pre-dates Cygnus CVS. Anyway, the question of what to do when the register's value can't be found has been largely ignored. I'm thinking that throwing an error would be a safer strategy - there is too much code ignoring register fetches and I don't think we're going to be auditing it soon. Andrew