public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: "Terekhov, Mikhail" <Mikhail.Terekhov@dell.com>,
	Luis Machado <luis.machado@arm.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	"gdb@sourceware.org" <gdb@sourceware.org>
Cc: Pedro Alves <pedro@palves.net>
Subject: RE: [RFC] Removing in process agent (IPA)
Date: Fri, 14 Jun 2024 09:08:06 +0100	[thread overview]
Message-ID: <87sexg7xqx.fsf@redhat.com> (raw)
In-Reply-To: <DM5PR1901MB21503622B1157CAAEF4F4F49E5C12@DM5PR1901MB2150.namprd19.prod.outlook.com>

"Terekhov, Mikhail" <Mikhail.Terekhov@dell.com> writes:

>> -----Original Message-----
>> From: Luis Machado <luis.machado@arm.com>
>>
>> Similarly, I also think it might be time to consider dropping the tracepoints
>> (mainly static and fast) machinery from gdbserver, as I suspect that is another
>> mechanism that is not being used very often.
>>
> We use tracepoints in our stub from the last millennia I guess (back from EMC days)
> and plan to do so in the future.
>
>> I recall trying to use tracepoints for practical purposes (back in the day), and it
>> wasn't up to the task, being too cumbersome to use, having bad failure modes
>
> Putting some UI/GUI on top of it makes it relatively simple to use.
>
>> and having other security implications when trying to debug stuff in
>> production platforms. The remote protocol side of it is OK, but again, I bet no
>> debugging stubs are using that anymore.
>
> We do use them but not in production though.

Just so I'm clear, you're talking about tracepoints here either in
gdbserver, or at least (if you have your own stub) in GDB and the remote
protocol, right?

This doesn't require gdb to continue shipping the IPA right?  Or have I
failed to understand your position?

Thanks,
Andrew


  parent reply	other threads:[~2024-06-14  8:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 14:17 Andrew Burgess
2024-06-13 15:08 ` Luis Machado
2024-06-13 16:38   ` Tom Tromey
2024-06-13 18:11   ` Terekhov, Mikhail
2024-06-14  7:54     ` Luis Machado
2024-06-14 13:47       ` Terekhov, Mikhail
2024-06-14  8:08     ` Andrew Burgess [this message]
2024-06-14 13:42       ` Terekhov, Mikhail
2024-06-14 13:48       ` Simon Marchi
2024-06-14 13:59         ` Luis Machado
2024-06-15 10:28           ` 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=87sexg7xqx.fsf@redhat.com \
    --to=aburgess@redhat.com \
    --cc=Mikhail.Terekhov@dell.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).