From: Tom Tromey <tom@tromey.com>
To: Luis Machado <luis.machado@arm.com>
Cc: Andrew Burgess <aburgess@redhat.com>,
gdb-patches@sourceware.org, gdb@sourceware.org,
Pedro Alves <pedro@palves.net>
Subject: Re: [RFC] Removing in process agent (IPA)
Date: Thu, 13 Jun 2024 10:38:14 -0600 [thread overview]
Message-ID: <87h6dwer2h.fsf@tromey.com> (raw)
In-Reply-To: <c9cfdbe4-c224-458d-b2fd-e84d7f109f96@arm.com> (Luis Machado's message of "Thu, 13 Jun 2024 16:08:00 +0100")
>> I'd like to have a conversation about whether or not we want to keep the
>> in-process-agent (IPA or libinproctrace.so).
Maybe you should ask on gdb@.
I personally have never used tracepoints or IPA. However, I'm not
exactly in the target audience, either, since most of my debugging is on
gdb itself.
Luis> Similarly, I also think it might be time to consider dropping the tracepoints
Luis> (mainly static and fast) machinery from gdbserver, as I suspect that is another
Luis> mechanism that is not being used very often.
Something I found out relatively recently is that agent expressions are
useful for letting gdbserver evaluate (some) breakpoint conditions.
This happens automatically, when possible, and greatly improves
performance.
So, while I don't really mind either way about tracepoints, if we do
remove these we should be careful to keep this part.
Tom
next prev parent reply other threads:[~2024-06-13 16:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 14:17 Andrew Burgess via Gdb
2024-06-13 15:08 ` Luis Machado via Gdb
2024-06-13 16:38 ` Tom Tromey [this message]
2024-06-13 18:11 ` Terekhov, Mikhail via Gdb
2024-06-14 7:54 ` Luis Machado via Gdb
2024-06-14 13:47 ` Terekhov, Mikhail via Gdb
2024-06-14 8:08 ` Andrew Burgess via Gdb
2024-06-14 13:42 ` Terekhov, Mikhail via Gdb
2024-06-14 13:48 ` Simon Marchi via Gdb
2024-06-14 13:59 ` Luis Machado via Gdb
2024-06-15 10:28 ` Andrew Burgess via Gdb
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=87h6dwer2h.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.org \
--cc=luis.machado@arm.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