From: Tom Tromey <tromey@adacore.com>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: Tom Tromey <tromey@adacore.com>, Keith Seitz <keiths@redhat.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] Allow 'ptype/o' for assembly
Date: Mon, 14 Nov 2022 06:32:36 -0700 [thread overview]
Message-ID: <874jv1y83v.fsf@tromey.com> (raw)
In-Reply-To: <9767e2c450d88795f0a2c47e3c4b78681447bfd9.camel@skynet.be> (Philippe Waroquiers's message of "Fri, 11 Nov 2022 20:50:23 +0100")
>>>>> "Philippe" == Philippe Waroquiers <philippe.waroquiers@skynet.be> writes:
Philippe> At work, I relatively often use ptype/o for Ada types.
Philippe> As it only works in C mode, as part of our zillions of site aliases,
Philippe> we have added:
Philippe> alias Wc = with language c -- with annotate 0 --
Philippe> (where annotate 0 avoids spurious language switch messages in the output).
Philippe> So, waiting for Adacore to implement ptype/o for Ada (hint hint :)),
Philippe> we use e.g.
Philippe> (gdb) Wc ptype/o sometype
I've considered it, and maybe the basics aren't too hard to do, but I
didn't really know what to do with types that have a dynamic layout.
Here the offsets would maybe have to be symbolic (which I'd suppose is a
pain to implement) and holes couldn't really be determined.
Maybe gdb could just print a warning in this scenario and drop the '/o'
modifier. That might be easier to do.
Tom
next prev parent reply other threads:[~2022-11-14 13:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 20:14 Tom Tromey
2022-11-08 21:19 ` Keith Seitz
2022-11-09 15:28 ` Tom Tromey
2022-11-11 19:50 ` Philippe Waroquiers
2022-11-14 13:32 ` Tom Tromey [this message]
2022-11-14 20:05 ` Philippe Waroquiers
2022-11-09 14:47 ` Andrew Burgess
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=874jv1y83v.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.com \
--cc=philippe.waroquiers@skynet.be \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).