From: Luis Machado <luis.machado@arm.com>
To: "Terekhov, Mikhail" <Mikhail.Terekhov@dell.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"gdb@sourceware.org" <gdb@sourceware.org>
Cc: Pedro Alves <pedro@palves.net>, Andrew Burgess <aburgess@redhat.com>
Subject: Re: [RFC] Removing in process agent (IPA)
Date: Fri, 14 Jun 2024 08:54:53 +0100 [thread overview]
Message-ID: <8b269edf-1e66-4c27-a175-56a9ef836cdf@arm.com> (raw)
In-Reply-To: <DM5PR1901MB21503622B1157CAAEF4F4F49E5C12@DM5PR1901MB2150.namprd19.prod.outlook.com>
Hi Mikhail,
Thanks for the input.
On 6/13/24 19:11, Terekhov, Mikhail wrote:
>> -----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.
Is it a custom remote debugging stub that uses tracepoints through the RSP packets gdb
sends? As opposed to using tracepoints through gdbserver itself?
>
>> 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.>
> Regards,
> Mikhail
>
> Internal Use - Confidential
next prev parent reply other threads:[~2024-06-14 7:55 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 [this message]
2024-06-14 13:47 ` Terekhov, Mikhail
2024-06-14 8:08 ` Andrew Burgess
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=8b269edf-1e66-4c27-a175-56a9ef836cdf@arm.com \
--to=luis.machado@arm.com \
--cc=Mikhail.Terekhov@dell.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.org \
--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).