Re: Don't disable the current display in throw_exception

Daniel Jacobowitz
2011-08-09T18:20:09Z

On Mon, Aug 8, 2011 at 10:28 AM, Pedro Alves <pedro@codesourcery.com> wrote:
> On Friday 05 August 2011 21:22:28, Daniel Jacobowitz wrote:
>> Seconded!  Does this also fix the bug where if you display a variable,
>> and it is temporarily at a bad address, the display is disabled?
>
> Nope...
>
>> Or is that still the case?  That always drives me nuts - yes, I know foo
>> is NULL, but I want GDB to go back to displaying *foo when it comes
>> back.
>
> That one doesn't look hard.  Below's a quick patch at it (not regtested).
> Here's what I get:
>
> (top-gdb) display
> 2: *argv = 0x7fffffffe37c "/home/pedro/gdb/try_catch/build/gdb/gdb"
> (top-gdb) p argv = 0
> $2 = (char **) 0x0
> (top-gdb) display
> 2: *argv = <error: Cannot access memory at address 0x0>

At a glance, the patch looks good to me - and I think the output is a
huge improvement.

> Do I still get cookie? :-P :-)

Sure, here's one:

ID=ba7d44f129f0edf3:FF=0:TM=1312913790:LM=1312913790:S=DnGFaNl9wLPTTtLM

Careful what you ask for...

--
Thanks,
Daniel