From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: "Simon Marchi" <simon.marchi@polymtl.ca>,
"Thomas Weißschuh" <thomas@t-8ch.de>
Cc: gdb@sourceware.org
Subject: Re: Remote query for structure layout
Date: Mon, 29 Mar 2021 22:02:50 +0200 [thread overview]
Message-ID: <be2a7685a700764fb52630ef1efb9d976e1ca99e.camel@skynet.be> (raw)
In-Reply-To: <63fba577-8dfd-f04b-2bc4-64645a084328@polymtl.ca>
On Mon, 2021-03-29 at 15:42 -0400, Simon Marchi via Gdb wrote:
> So I would lean towards a home-grown format, but it's more work to
> ensure it is extensible if we want to include more information in the
> replies in the future.
Wouldn't it be possible to have the target sending back some (maybe limited
and/or partial) 'standard debug info' (such as dwarf) for these types ?
I have a very limited knowledge of dwarf, so no idea if it is easy
to have 'small scale' debug info being returned by the target
(e.g. by having the needed dwarf entries linked as binary data
inside the target, or generated by the target).
This might allow to reuse the existing GDB dwarf parser and likely
give a flexible enough description 'language'.
Philippe
next prev parent reply other threads:[~2021-03-29 20:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 11:06 Thomas Weißschuh
2021-03-29 16:05 ` Simon Marchi
2021-03-29 17:33 ` Thomas Weißschuh
2021-03-29 19:42 ` Simon Marchi
2021-03-29 20:02 ` Philippe Waroquiers [this message]
2021-03-29 20:10 ` Simon Marchi
2021-03-29 20:20 ` Philippe Waroquiers
[not found] <mailman.6.1616932808.1485743.gdb@sourceware.org>
2021-03-30 20:35 ` Tim Newsome
2021-03-30 21:33 ` Simon Marchi
2021-03-30 21:41 ` David Blaikie
2021-03-30 21:49 ` Simon Marchi
2021-03-30 22:03 ` David Blaikie
2021-03-30 22:38 ` Simon Marchi
2021-03-30 22:44 ` David Blaikie
2021-03-31 0:16 ` Simon Marchi
2021-03-31 3:27 ` David Blaikie
2021-03-31 13:00 ` Simon Marchi
2021-04-02 22:05 ` David Blaikie
2021-04-03 19:39 ` Simon Marchi
2021-03-31 14:06 ` Tim Newsome
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=be2a7685a700764fb52630ef1efb9d976e1ca99e.camel@skynet.be \
--to=philippe.waroquiers@skynet.be \
--cc=gdb@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=thomas@t-8ch.de \
/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).