Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Ezra Sitorus <ezra.sitorus@arm.com>
To: Andrew Burgess <aburgess@redhat.com>
Cc: <gdb-patches@sourceware.org>, <luis.machado.foss@gmail.com>,
	<pedro@palves.net>
Subject: Re: [RFC PATCH] gdb/py: Add pretty printer for __mfp8 for aarch64
Date: Wed, 26 Nov 2025 16:08:23 +0000	[thread overview]
Message-ID: <aScl97TyfcxbM5tD@D2G2X7XGD1> (raw)
In-Reply-To: <87wm3ntgd9.fsf@redhat.com>

> I think you ideally want these to be automatically registered, just how
> compiler pretty printers would be automatically loaded.
> 
> You should investigate the 'new_objfile' event.  But I'm not certain how
> you're going to decide if the pretty printer should be registered or
> not as you'll only want to register this for suitable AArch64 inferiors
> I guess.  Maybe there's something that could be done via the program
> space? 
> 
> My concern is that if these printers don't auto-register then users
> aren't going to know this feature exists. 

I've been taking a look at this. Am I right in thinking that even if use
the new_objfile event, I would still do one of these:

1) Manually write the python lines like in my example
2) Add the python lines to .gdbinit
3) Write in a python file and then source it in gdb

Is there anyway to auto-register this without having to do any manual
work?

Ezra

  parent reply	other threads:[~2025-11-26 16:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-18 14:14 Ezra.Sitorus
2025-11-18 17:12 ` Andrew Burgess
2025-11-18 18:37   ` Ezra Sitorus
2025-11-26 16:08   ` Ezra Sitorus [this message]
2025-11-18 18:42 ` Tom Tromey
2025-11-19 13:12   ` Ezra Sitorus
2025-11-19 15:58     ` Tom Tromey
2025-11-19 21:28       ` Ezra Sitorus
2025-12-16 16:39       ` Ezra Sitorus

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=aScl97TyfcxbM5tD@D2G2X7XGD1 \
    --to=ezra.sitorus@arm.com \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luis.machado.foss@gmail.com \
    --cc=pedro@palves.net \
    /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