From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/1] Integrate GNU poke in GDB
Date: Wed, 12 May 2021 12:14:50 +0200 [thread overview]
Message-ID: <877dk4mf6t.fsf@oracle.com> (raw)
In-Reply-To: <20210512085256.GV6612@embecosm.com> (Andrew Burgess's message of "Wed, 12 May 2021 09:52:56 +0100")
>> If you map a BTF_Type from GDB, it will check the integrity (poke also
>> support mapping in non-strict mode) and also will build the structure
>> based on the very contents. GDB simply can't do the same thing based on
>> the "equivalent" collection of decoupled C types, which are really not
>> equivalent at all.
>
> Thanks for this explanation. For me, personally, I think the manual
> entry would be much more powerful if something like the above was
> included. I feel it really gives an idea for the sort of thing that
> can be achieved with poke.
Ok I am adding a section to poke.texi with an introduction.
Thanks for the feedback!
next prev parent reply other threads:[~2021-05-12 10:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 15:10 [PATCH 0/1] " Jose E. Marchesi
2021-05-10 15:10 ` [PATCH 1/1] " Jose E. Marchesi
2021-05-10 16:56 ` Eli Zaretskii
2021-05-10 18:49 ` Jose E. Marchesi
2021-05-10 18:52 ` Eli Zaretskii
2021-05-11 7:33 ` Andrew Burgess
2021-05-11 13:07 ` Jose E. Marchesi
2021-05-12 8:52 ` Andrew Burgess
2021-05-12 10:14 ` Jose E. Marchesi [this message]
2021-05-13 16:59 ` Tom Tromey
2021-05-10 18:39 ` [PATCH 0/1] " Simon Marchi
2021-05-10 20:07 ` Jose E. Marchesi
2021-05-11 6:25 ` Andrew Burgess
2021-05-13 17:04 ` Tom Tromey
2021-05-11 18:56 ` Tom Tromey
2021-05-12 8:06 ` Jose E. Marchesi
2021-05-13 15:52 ` Tom Tromey
2021-05-14 20:52 ` Jose E. Marchesi
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=877dk4mf6t.fsf@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
/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).