This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Don't disable the current display in throw_exception
- From: Daniel Jacobowitz <drow at false dot org>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: Pedro Alves <pedro at codesourcery dot com>, gdb-patches at sourceware dot org
- Date: Fri, 5 Aug 2011 16:22:28 -0400
- Subject: Re: Don't disable the current display in throw_exception
- References: <201108051553.02017.pedro@codesourcery.com> <m3r54zx5bq.fsf@fleche.redhat.com>
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? 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. I don't know what the "infinite recursion" in question is.
On Fri, Aug 5, 2011 at 11:10 AM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
>
> Pedro> An unavailable exception is thrown while evaluating
> Pedro> the dwarf location of argc, but that is caught by higher
> Pedro> layers, and shouldn't cause a disablement of the display.
> Pedro> Patch below fixes it, and adds a test that would
> Pedro> fail otherwise, for me at least, on amd64-linux.
>
> Thanks for doing this.
>
> Tom
>
--
Thanks,
Daniel