From: Andrew Burgess <aburgess@redhat.com>
To: Simon Marchi <simon.marchi@efficios.com>,
gdb-patches@sourceware.org, binutils@sourceware.org
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH 12/13] gdb/remote: remove uses of sprintf
Date: Mon, 17 Aug 2026 17:51:21 +0100 [thread overview]
Message-ID: <878q643d2u.fsf@redhat.com> (raw)
In-Reply-To: <20260817151646.152571-13-simon.marchi@efficios.com>
Simon Marchi <simon.marchi@efficios.com> writes:
> When building on macOS, I get some:
>
> /Users/smarchi/src/binutils-gdb/gdb/remote.c:11556:3: error: 'sprintf' is deprecated: This function is provided for compatibility reasons only. Due to security concerns inherent in the design of sprintf(3), it is highly recommended that you use snprintf(3) instead. [-Werror,-Wdeprecated-declarations]
> 11556 | sprintf (buf, ";cmds:%x,", bp_tgt->persist);
> | ^
>
> Both are in remote_add_target_side_commands, which unlike the similar
> remote_add_target_side_condition, does not receive the end of the
> packet, and does not bound its writes. Give it a BUF_END parameter,
> and use xsnprintf.
>
> The edits to remote_add_target_side_condition are to keep the two
> functions in sync.
>
> Ideally, the pack_hex_byte calls and the `*buf = '\0'` assignments
> should also have some bound checks, but that is outside the scope of
> this patch.
>
> Change-Id: Ib2e9849d89ebcc9e6275297138a3deb8bf03a7c3
> ---
> gdb/remote.c | 36 ++++++++++++++++++++++--------------
> 1 file changed, 22 insertions(+), 14 deletions(-)
>
> diff --git a/gdb/remote.c b/gdb/remote.c
> index 3d38a9c7c8c9..fe898013a394 100644
> --- a/gdb/remote.c
> +++ b/gdb/remote.c
> @@ -11513,10 +11513,11 @@ Remote replied unexpectedly while setting startup-with-shell: %s"),
> }
> \f
>
> -/* Given a location's target info BP_TGT and the packet buffer BUF, output
> - the list of conditions (in agent expression bytecode format), if any, the
> - target needs to evaluate. The output is placed into the packet buffer
> - started from BUF and ended at BUF_END. */
> +/* Given a location's target info BP_TGT and the packet buffer BUF, output the
> + list of conditions (in agent expression bytecode format), if any, the
> + target needs to evaluate.
> +
> + The output is appended to the existing content of BUF. */
>
> static int
> remote_add_target_side_condition (struct gdbarch *gdbarch,
> @@ -11532,35 +11533,42 @@ remote_add_target_side_condition (struct gdbarch *gdbarch,
> /* Send conditions to the target. */
> for (agent_expr *aexpr : bp_tgt->conditions)
> {
> - xsnprintf (buf, buf_end - buf, "X%x,", (int) aexpr->buf.size ());
> - buf += strlen (buf);
> + buf += xsnprintf (buf, buf_end - buf, "X%x,", (int) aexpr->buf.size ());
> +
> for (int i = 0; i < aexpr->buf.size (); ++i)
> buf = pack_hex_byte (buf, aexpr->buf[i]);
> +
I wonder if we should add an assert here either inside, or just after,
the loop, to check that we've not blown past BUF_END? Unless I'm
misunderstanding this, these PACK_HEX_BYTE calls could overrun the
buffer, right?
> *buf = '\0';
> }
> return 0;
> }
>
> +/* Given a location's target info BP_TGT and the packet buffer BUF, output the
> + list of commands (in agent expression bytecode format), if any, the target
> + needs to run when the breakpoint is hit.
> +
> + The output is appended to the existing content of BUF. */
> +
> static void
> remote_add_target_side_commands (struct gdbarch *gdbarch,
> - struct bp_target_info *bp_tgt, char *buf)
> + struct bp_target_info *bp_tgt, char *buf,
> + char *buf_end)
> {
> if (bp_tgt->tcommands.empty ())
> return;
>
> buf += strlen (buf);
> -
> - sprintf (buf, ";cmds:%x,", bp_tgt->persist);
> - buf += strlen (buf);
> + buf += xsnprintf (buf, buf_end - buf, ";cmds:%x,", bp_tgt->persist);
>
> /* Concatenate all the agent expressions that are commands into the
> cmds parameter. */
> for (agent_expr *aexpr : bp_tgt->tcommands)
> {
> - sprintf (buf, "X%x,", (int) aexpr->buf.size ());
> - buf += strlen (buf);
> + buf += xsnprintf (buf, buf_end - buf, "X%x,", (int) aexpr->buf.size ());
> +
> for (int i = 0; i < aexpr->buf.size (); ++i)
> buf = pack_hex_byte (buf, aexpr->buf[i]);
> +
As above for buffer overrun maybe?
Thanks,
Andrew
> *buf = '\0';
> }
> }
> @@ -11604,7 +11612,7 @@ remote_target::insert_breakpoint (struct gdbarch *gdbarch,
> remote_add_target_side_condition (gdbarch, bp_tgt, p, endbuf);
>
> if (can_run_breakpoint_commands ())
> - remote_add_target_side_commands (gdbarch, bp_tgt, p);
> + remote_add_target_side_commands (gdbarch, bp_tgt, p, endbuf);
>
> putpkt (rs->buf);
> getpkt (&rs->buf);
> @@ -11912,7 +11920,7 @@ remote_target::insert_hw_breakpoint (struct gdbarch *gdbarch,
> remote_add_target_side_condition (gdbarch, bp_tgt, p, endbuf);
>
> if (can_run_breakpoint_commands ())
> - remote_add_target_side_commands (gdbarch, bp_tgt, p);
> + remote_add_target_side_commands (gdbarch, bp_tgt, p, endbuf);
>
> putpkt (rs->buf);
> getpkt (&rs->buf);
> --
> 2.55.0
next prev parent reply other threads:[~2026-08-17 16:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 15:16 [PATCH 00/13] Fix various warnings when building on macOS Simon Marchi
2026-08-17 15:16 ` [PATCH 01/13] gdbsupport: remove uses of vsprintf Simon Marchi
2026-08-17 15:47 ` Andrew Burgess
2026-08-17 15:16 ` [PATCH 02/13] gdbsupport: remove uses of sprintf Simon Marchi
2026-08-17 15:49 ` Andrew Burgess
2026-08-17 15:16 ` [PATCH 03/13] opcodes/z80: remove use " Simon Marchi
2026-08-18 6:40 ` Jan Beulich
2026-08-18 16:48 ` Simon Marchi
2026-08-17 15:16 ` [PATCH 04/13] sim/ppc: make defines.h sed command portable Simon Marchi
2026-08-17 15:36 ` Andrew Burgess
2026-08-17 15:16 ` [PATCH 05/13] sim/m32r: fix unused variable warning on non-Linux hosts Simon Marchi
2026-08-17 15:36 ` Andrew Burgess
2026-08-17 15:16 ` [PATCH 06/13] sim/m32r: fix unused function warnings " Simon Marchi
2026-08-17 15:37 ` Andrew Burgess
2026-08-17 15:16 ` [PATCH 07/13] gdb/csky: remove uses of sprintf Simon Marchi
2026-08-17 16:26 ` Andrew Burgess
2026-08-17 17:03 ` Simon Marchi
2026-08-17 20:50 ` Tom Tromey
2026-08-18 18:26 ` Simon Marchi
2026-08-17 15:16 ` [PATCH 08/13] gdb/dwarf2: " Simon Marchi
2026-08-17 16:35 ` Andrew Burgess
2026-08-17 15:16 ` [PATCH 09/13] gdb/elfread: remove use " Simon Marchi
2026-08-17 16:38 ` Andrew Burgess
2026-08-17 15:16 ` [PATCH 10/13] gdbsupport: add xstrcpy Simon Marchi
2026-08-17 16:45 ` Andrew Burgess
2026-08-17 17:30 ` Simon Marchi
2026-08-17 15:16 ` [PATCH 11/13] gdb/remote-fileio: remove uses of sprintf Simon Marchi
2026-08-17 16:53 ` Andrew Burgess
2026-08-17 15:16 ` [PATCH 12/13] gdb/remote: " Simon Marchi
2026-08-17 16:51 ` Andrew Burgess [this message]
2026-08-17 17:34 ` Simon Marchi
2026-08-17 15:16 ` [PATCH 13/13] gdb/tracepoint: " Simon Marchi
2026-08-17 16:51 ` Andrew Burgess
2026-08-17 20:52 ` [PATCH 00/13] Fix various warnings when building on macOS Tom Tromey
2026-08-18 18:10 ` 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=878q643d2u.fsf@redhat.com \
--to=aburgess@redhat.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.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