From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-prs-return-9552-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Received: (qmail 23725 invoked by alias); 28 Jan 2011 18:35:52 -0000
Received: (qmail 23589 invoked by uid 22791); 28 Jan 2011 18:35:51 -0000
X-SWARE-Spam-Status: No, hits=-2.6 required=5.0
	tests=ALL_TRUSTED,AWL,BAYES_00,TW_MJ,TW_XF
X-Spam-Check-By: sourceware.org
Received: from localhost (HELO sourceware.org) (127.0.0.1)
    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 28 Jan 2011 18:35:48 +0000
From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/12425] Confusing python backtrace on iterator end
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: python
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mjw at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: tromey at redhat dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-12425-4717-DhrE9MLS2w@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-12425-4717@http.sourceware.org/bugzilla/>
References: <bug-12425-4717@http.sourceware.org/bugzilla/>
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Date: Fri, 28 Jan 2011 18:35:00 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
X-SW-Source: 2011-q1/txt/msg00093.txt.bz2

http://sourceware.org/bugzilla/show_bug.cgi?id=12425

--- Comment #3 from Mark Wielaard <mjw at redhat dot com> 2011-01-28 18:35:34 UTC ---
(In reply to comment #2)
> With cvs head gdb I get:
> 
> (gdb) p it
> $1 = {
>   first = 
>     <error reading variable: Cannot access memory at address 0xfffffff5>, 
>   second = {
>     a = 134524960, 
>     b = 1
>   }
> }
> 
> I think that seems a lot more reasonable.

Yes, much more reasonable, thanks.

Although I think it is still a but too verbose.
Ideally (for me) the default would just have a short indicator
(say "<???>") that tells me the value couldn't be determined.
Then if I would like to see why that is (p /v maybe) it would
display all the extra explanations.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.