[Bug python/12425] Confusing python backtrace on iterator end

[mjw at redhat dot com]

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.