From: Daniel Jacobowitz <drow@false.org>
To: Tom Tromey <tromey@redhat.com>
Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: Don't disable the current display in throw_exception
Date: Fri, 05 Aug 2011 20:22:00 -0000 [thread overview]
Message-ID: <CAN9gPaHTbvcY9_=TYfSKyA1XPRYPuZbwTBn=YTngJx+qfrkf9Q@mail.gmail.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2011-08-05 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 14:53 Pedro Alves
2011-08-05 15:10 ` Tom Tromey
2011-08-05 20:22 ` Daniel Jacobowitz [this message]
2011-08-08 14:28 ` Pedro Alves
2011-08-09 16:23 ` Don't disable displays on display eval error (Re: Don't disable the current display in throw_exception) Pedro Alves
2011-08-09 18:20 ` Don't disable the current display in throw_exception Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN9gPaHTbvcY9_=TYfSKyA1XPRYPuZbwTBn=YTngJx+qfrkf9Q@mail.gmail.com' \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox