From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH 02/10] [gdb] Add missing i18n support to error strings (part 2)
Date: Sun, 7 Jun 2026 08:00:33 +0200 [thread overview]
Message-ID: <20260607060041.410491-3-tdevries@suse.de> (raw)
In-Reply-To: <20260607060041.410491-1-tdevries@suse.de>
Add missing i18n support to some error strings.
Result of:
...
$ find gdb* -type f -name "*.[ch]" -o -name "*.cc" \
| egrep -v /testsuite/ \
| xargs sed -i \
'/"[ \t]*%s[ \t]*"/b l;s/\([ \t]\)error (\("[^"]*"\),$/\1error (_(\2),/;:l'
...
---
gdb/procfs.c | 2 +-
gdbserver/thread-db.cc | 4 ++--
gdbserver/tracepoint.cc | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/gdb/procfs.c b/gdb/procfs.c
index 7472c10616e..fd5d1a76bd6 100644
--- a/gdb/procfs.c
+++ b/gdb/procfs.c
@@ -599,7 +599,7 @@ static void
proc_error (procinfo *pi, const char *func, int line)
{
int saved_errno = errno;
- error ("procfs: %s line %d, %s: %s",
+ error (_("procfs: %s line %d, %s: %s"),
func, line, pi->pathname, safe_strerror (saved_errno));
}
diff --git a/gdbserver/thread-db.cc b/gdbserver/thread-db.cc
index 0bdcda2ced8..fd78ee8a208 100644
--- a/gdbserver/thread-db.cc
+++ b/gdbserver/thread-db.cc
@@ -178,13 +178,13 @@ find_one_thread (ptid_t ptid)
td_err_e err = thread_db->td_ta_map_lwp2thr_p (thread_db->thread_agent, lwpid,
&th);
if (err != TD_OK)
- error ("Cannot get thread handle for LWP %d: %s",
+ error (_("Cannot get thread handle for LWP %d: %s"),
lwpid, thread_db_err_str (err));
td_thrinfo_t ti;
err = thread_db->td_thr_get_info_p (&th, &ti);
if (err != TD_OK)
- error ("Cannot get thread info for LWP %d: %s",
+ error (_("Cannot get thread info for LWP %d: %s"),
lwpid, thread_db_err_str (err));
threads_debug_printf ("Found thread %ld (LWP %d)",
diff --git a/gdbserver/tracepoint.cc b/gdbserver/tracepoint.cc
index 60c8926bb8b..3d3f0776fc0 100644
--- a/gdbserver/tracepoint.cc
+++ b/gdbserver/tracepoint.cc
@@ -6047,7 +6047,7 @@ upload_fast_traceframes (void)
if (read_inferior_memory (tf
+ offsetof (struct traceframe, data),
block, ipa_tframe.data_size))
- error ("Uploading: Couldn't read traceframe data at %s\n",
+ error (_("Uploading: Couldn't read traceframe data at %s\n"),
paddress (tf + offsetof (struct traceframe, data)));
}
--
2.51.0
next prev parent reply other threads:[~2026-06-07 6:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-07 6:00 [PATCH 00/10] [gdb] Add some missing i18n support Tom de Vries
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 ` Tom de Vries [this message]
2026-06-09 16:56 ` [PATCH 02/10] [gdb] Add missing i18n support to error strings (part 2) 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-3-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