From: Doug Evans <dje@google.com>
To: "Tedeschi, Walfred" <walfred.tedeschi@intel.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH][PR python/17364] Cleanup registration of __gdb_builtin_type_bound128 pretty-printer
Date: Thu, 09 Oct 2014 16:23:00 -0000 [thread overview]
Message-ID: <CADPb22TBPdF9dMmbYXhoS98V_YeU0hY50qfYJwDKxb=6Mk0ioA@mail.gmail.com> (raw)
In-Reply-To: <AC542571535E904D8E8ADAE745D60B192F92CA48@IRSMSX104.ger.corp.intel.com>
On Mon, Oct 6, 2014 at 12:33 AM, Tedeschi, Walfred
<walfred.tedeschi@intel.com> wrote:
> Hi Doug,
>
> I have also submitted a patch for this last week. Though I was not creating a new directory for pretty printers.
> https://sourceware.org/ml/gdb-patches/2014-09/msg00867.html
>
> I would like though to understand a bit more your comment on having x86 on the name of the register. What is the purpose of that?
> (I could change it in case)
Imagine a multi-arch gdb with several arches having bounds registers.
How do we distinguish them in the pretty-printer namespace?
> About registration of the pretty printer. We could do the following:
> 1. Register an event listener for new obj_files.
> 2. Query at every event the architecture of the inferior. (In case we had an event new_inferior loaded it would be cheaper.)
> 3. In case of x86 or amd64 we can then register the pretty-printer for the bound registers.
We could do something like that for 7.9 alright.
At the moment it feels like a bit of overkill just for one pretty-printer.
And for 7.8.1 I want to do something simple.
next prev parent reply other threads:[~2014-10-09 16:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-04 18:47 Doug Evans
2014-10-06 7:34 ` Tedeschi, Walfred
2014-10-09 16:23 ` Doug Evans [this message]
2014-10-13 6:57 ` Tedeschi, Walfred
2014-10-13 18:09 ` Doug Evans
2014-10-07 12:17 ` Phil Muldoon
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='CADPb22TBPdF9dMmbYXhoS98V_YeU0hY50qfYJwDKxb=6Mk0ioA@mail.gmail.com' \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=walfred.tedeschi@intel.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