From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30530 invoked by alias); 16 Apr 2009 18:02:02 -0000 Received: (qmail 30361 invoked by uid 22791); 16 Apr 2009 18:02:00 -0000 X-SWARE-Spam-Status: No, hits=-2.4 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; Thu, 16 Apr 2009 18:01:52 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 434932BAC61; Thu, 16 Apr 2009 14:01:51 -0400 (EDT) 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 JXygQmaBO7Nk; Thu, 16 Apr 2009 14:01:51 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 0CACA2BAB6A; Thu, 16 Apr 2009 14:01:50 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id EEE54F58C1; Thu, 16 Apr 2009 11:01:46 -0700 (PDT) Date: Thu, 16 Apr 2009 18:02:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: gdb-patches@sourceware.org Subject: Re: [RFA] print error message if (auto) disassembly failed Message-ID: <20090416180146.GH7585@adacore.com> References: <20090416173918.GP7557@adacore.com> <834owolc51.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <834owolc51.fsf@gnu.org> User-Agent: Mutt/1.5.18 (2008-05-17) 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: 2009-04/txt/msg00376.txt.bz2 > How about > > #0 0x00007f8befcc8307 in ?? () > 0x00007f8befcc8307: (bad) > > instead? This is consistent with what "display/i $pc" displays if $pc > has a bad value, such as if you somehow land in the middle of an > instruction. The problem is that this is not actually a "bad" instruction in this case, but an invalid address. So I think that the "Cannot read memory at ..." error message is more accurate. -- Joel