From: Luis <luis.machado.foss@gmail.com>
To: Tom Tromey <tromey@adacore.com>
Cc: Guinevere Larsen <guinevere@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/3] Use gnulib c-ctype module, not <ctype.h>
Date: Thu, 16 Oct 2025 22:50:57 +0100 [thread overview]
Message-ID: <CANnS9rug2whY=s5giZncRVTJzXiknOUSKFq++qCkHAC9oasNZw@mail.gmail.com> (raw)
In-Reply-To: <878qhasw3q.fsf@tromey.com>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
On Thu, Oct 16, 2025, 16:30 Tom Tromey <tromey@adacore.com> wrote:
> Tom> Another option would be to write our own thing akin to "c-ctype" but
> Tom> that uses the libiberty code instead. That would work since
> Tom> libinproctrace.so seems to link against libiberty.
>
> I tried this but forgot that libinproctrace.so does not use gdbsupport
> either.
>
> I strongly dislike how libinproctrace.so was implemented. A bunch of
> cpp conditions in random files seems a lot worse than just having
> separate sources, since the rules for the IPA and non-IPA cases are
> different.
>
> Tom
>
Does anybody else think it might be time for the IPA to go? It feels like
it is one of those bits that almost nobody uses nowadays and maintenance
hasn't kept up, and it gets in the way of newer changes.
If tracepoints are seldom used in gdbserver, the IPA seems even more niche.
>
[-- Attachment #2: Type: text/html, Size: 1510 bytes --]
next prev parent reply other threads:[~2025-10-16 21:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 13:13 Tom Tromey
2025-08-06 13:13 ` [PATCH 1/3] Import the c-ctype module from gnulib Tom Tromey
2025-08-06 13:13 ` [PATCH 2/3] Use c-ctype.h (not safe-ctype.h) in gdb Tom Tromey
2025-08-06 13:13 ` [PATCH 3/3] Use gnulib c-ctype module " Tom Tromey
2025-08-06 19:46 ` [PATCH 0/3] Use gnulib c-ctype module, not <ctype.h> Simon Marchi
2025-08-07 20:39 ` Tom Tromey
2025-08-20 17:14 ` Simon Marchi
2025-09-09 17:53 ` Tom Tromey
2025-09-09 18:01 ` Simon Marchi
2025-09-09 18:55 ` Tom Tromey
2025-10-14 13:00 ` Guinevere Larsen
2025-10-14 19:19 ` Tom Tromey
2025-10-16 15:30 ` Tom Tromey
2025-10-16 21:50 ` Luis [this message]
2025-10-21 12:59 ` Tom Tromey
2025-10-21 17:37 ` Simon Marchi
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='CANnS9rug2whY=s5giZncRVTJzXiknOUSKFq++qCkHAC9oasNZw@mail.gmail.com' \
--to=luis.machado.foss@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=guinevere@redhat.com \
--cc=tromey@adacore.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