Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess via Gdb <gdb@sourceware.org>
To: gdb-patches@sourceware.org, gdb@sourceware.org
Subject: [RFC] Removing in process agent (IPA)
Date: Thu, 13 Jun 2024 15:17:44 +0100	[thread overview]
Message-ID: <87y1797wqf.fsf@redhat.com> (raw)


Hi,

I'd like to have a conversation about whether or not we want to keep the
in-process-agent (IPA or libinproctrace.so).

A couple of recent patches[1][2] have triggered the question of whether
it would be better if we just dropped IPA from GDB.

We do have some tests that make use of IPA in gdb.trace/, so its no
untested code.

I'd describe myself as neutral on this topic.  I've never used the IPA
myself, but I have no real objections to it continuing to live on.
However, if nobody wants to keep it I'm happy to do to the work to
remove it from GDB.

So my question to the group: would anyone like to speak in favour of
keeping the IPA around?

Thanks,
Andrew

[1] https://inbox.sourceware.org/gdb-patches/cover.1706801009.git.aburgess@redhat.com
[2] https://inbox.sourceware.org/gdb-patches/f18d8f32e1e8af423e38efd0cb58ced1a98b5efb.1718271737.git.aburgess@redhat.com


             reply	other threads:[~2024-06-13 14:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 14:17 Andrew Burgess via Gdb [this message]
2024-06-13 15:08 ` Luis Machado via Gdb
2024-06-13 16:38   ` Tom Tromey
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=87y1797wqf.fsf@redhat.com \
    --to=gdb@sourceware.org \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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