From: Pedro Alves <pedro@palves.net>
To: Tom Tromey <tom@tromey.com>,
Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: Re: [PATCHv2] gdb/x86: handle stap probe arguments in xmm registers
Date: Thu, 17 Mar 2022 15:54:48 +0000 [thread overview]
Message-ID: <705bb6c9-6175-0d6d-7c3a-bcabade3f664@palves.net> (raw)
In-Reply-To: <871qz1ke0r.fsf@tromey.com>
On 2022-03-16 17:23, Tom Tromey wrote:
> Andrew> This is because GDB doesn't currently support placing non-scalar types
> Andrew> on the agent expression evaluation stack. Solving this is clearly
> Andrew> related to the original problem, but feels a bit like a second
> Andrew> problem. I'd like to get feedback on whether my approach to solving
> Andrew> the original problem is acceptable or not before I start looking at
> Andrew> how to handle xmm registers within agent expressions.
>
> Note that there are many things that can't be represented in agent
> expressions. I recall filing a bug report about this -- there are some
> DWARF expressions that can't be translated, and IIRC, floating point
> isn't handled at all. So, I wouldn't worry too much about this. My
> sense is that tracepoints aren't used a whole lot.
Yeah. They were definitely being used in production a few years back when we were
revamping them, adding support to gdbserver, etc. But it seems like users stopped using
them since. It's possible that the fact that more and more DWARF expressions
can't be converted carries some weight. Or users simply started using other
tools for the job.
In any case, if I were to tackle the whole problem set today, instead of extending agent
expressions bytecode to be able to do more of what DWARF can do, I'd be looking at expressing
what should be collected via DWARF expressions/locations. I mean, send DWARF expressions
to the target side to be evaluated.
next prev parent reply other threads:[~2022-03-17 15:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 10:54 [PATCH] " Andrew Burgess
2022-03-15 13:53 ` Metzger, Markus T
2022-03-15 17:28 ` Andrew Burgess
2022-03-16 9:36 ` Metzger, Markus T
2022-03-16 10:03 ` Andrew Burgess
2022-03-16 10:29 ` Metzger, Markus T
2022-03-16 14:13 ` [PATCHv2] " Andrew Burgess
2022-03-16 17:23 ` Tom Tromey
2022-03-17 15:54 ` Pedro Alves [this message]
2022-03-21 14:41 ` Andrew Burgess
2022-03-16 17:42 ` Tom Tromey
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=705bb6c9-6175-0d6d-7c3a-bcabade3f664@palves.net \
--to=pedro@palves.net \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).