From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH 00/10] [gdb] Add some missing i18n support
Date: Sun, 7 Jun 2026 08:00:31 +0200 [thread overview]
Message-ID: <20260607060041.410491-1-tdevries@suse.de> (raw)
I used a Claude Code session to identify spots in the GDB source code that are
missing i18n support.
I wrote patches to fix these, all but two using sed scripts.
I ignored internal_error and internal_warning calls, because I think their
strings don't classify as user-visible strings.
I also ignored calls like gdb_printf (gdb_stdlog, "Warning: ..."). I wonder
if these need to be rewritten to use warning ("...") instead.
Tested on x86_64-linux.
Tom de Vries (10):
[gdb] Add missing i18n support to error strings (part 1)
[gdb] Add missing i18n support to error strings (part 2)
[gdb] Add missing i18n support to error strings (part 3)
[gdb] Add missing i18n support to error strings (part 4)
[gdb] Add missing i18n support to errors strings (part 5)
[gdb] Add missing i18n support to warning strings (part 1)
[gdb] Add missing i18n support to warning strings (part 2)
[gdb] Add missing i18n support to warning strings (part 3)
[gdb] Add missing i18n support to warning strings (part 4)
[gdb] Add missing i18n support to warning strings (part 5)
gdb/break-cond-parse.c | 12 +++----
gdb/cli/cli-style.c | 4 +--
gdb/elfread.c | 4 +--
gdb/f-array-walker.h | 4 +--
gdb/f-lang.c | 2 +-
gdb/f-valprint.c | 2 +-
gdb/mi/mi-parse.c | 8 ++---
gdb/nat/fork-inferior.c | 6 ++--
gdb/ppc-sysv-tdep.c | 4 +--
gdb/procfs.c | 4 +--
gdb/s390-tdep.c | 4 +--
gdb/solib-rocm.c | 4 +--
gdb/symtab.c | 4 +--
gdb/valarith.c | 2 +-
gdb/windows-nat.c | 8 ++---
gdbserver/linux-low.cc | 36 ++++++++++-----------
gdbserver/linux-tic6x-low.cc | 2 +-
gdbserver/linux-x86-low.cc | 2 +-
gdbserver/mem-break.cc | 14 ++++----
gdbserver/netbsd-low.cc | 12 +++----
gdbserver/regcache.cc | 2 +-
gdbserver/remote-utils.cc | 14 ++++----
gdbserver/server.cc | 14 ++++----
gdbserver/thread-db.cc | 14 ++++----
gdbserver/tracepoint.cc | 58 +++++++++++++++++-----------------
gdbserver/win32-aarch64-low.cc | 2 +-
gdbserver/win32-i386-low.cc | 2 +-
gdbserver/win32-low.cc | 8 ++---
28 files changed, 126 insertions(+), 126 deletions(-)
base-commit: 0a6aadacb2e9a2695c82635dd8b2f7fccf537adf
--
2.51.0
next reply other threads:[~2026-06-07 6:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-07 6:00 Tom de Vries [this message]
2026-06-07 6:00 ` [PATCH 01/10] [gdb] Add missing i18n support to error strings (part 1) Tom de Vries
2026-06-07 6:00 ` [PATCH 02/10] [gdb] Add missing i18n support to error strings (part 2) Tom de Vries
2026-06-09 16:56 ` Tom Tromey
2026-06-10 6:10 ` Tom de Vries
2026-06-07 6:00 ` [PATCH 03/10] [gdb] Add missing i18n support to error strings (part 3) Tom de Vries
2026-06-07 6:00 ` [PATCH 04/10] [gdb] Add missing i18n support to error strings (part 4) Tom de Vries
2026-06-07 6:00 ` [PATCH 05/10] [gdb] Add missing i18n support to errors strings (part 5) Tom de Vries
2026-06-07 6:00 ` [PATCH 06/10] [gdb] Add missing i18n support to warning strings (part 1) Tom de Vries
2026-06-07 6:00 ` [PATCH 07/10] [gdb] Add missing i18n support to warning strings (part 2) Tom de Vries
2026-06-07 6:00 ` [PATCH 08/10] [gdb] Add missing i18n support to warning strings (part 3) Tom de Vries
2026-06-07 6:00 ` [PATCH 09/10] [gdb] Add missing i18n support to warning strings (part 4) Tom de Vries
2026-06-09 17:00 ` Tom Tromey
2026-06-07 6:00 ` [PATCH 10/10] [gdb] Add missing i18n support to warning strings (part 5) Tom de Vries
2026-06-09 17:01 ` [PATCH 00/10] [gdb] Add some missing i18n support Tom Tromey
2026-06-10 7:03 ` Tom de Vries
2026-06-10 13:21 ` Tom Tromey
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=20260607060041.410491-1-tdevries@suse.de \
--to=tdevries@suse.de \
--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