From: Richard Henderson <richard.henderson@linaro.org>
To: ~foxes <foxes687@andestech.com>, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH qemu 2/2] gdbstub: Fixed gdb_open() does not work issue while an extra 'x' is being added when converting '%s' to a pointer
Date: Tue, 20 Jun 2023 09:32:10 +0200 [thread overview]
Message-ID: <910efeb9-78c2-659c-3101-0e7dc3770ef5@linaro.org> (raw)
In-Reply-To: <168723238949.9156.9853906656288727865-1@git.sr.ht>
On 6/8/23 11:06, ~foxes wrote:
> From: Foxes Hung <foxes687@andestech.com>
>
> Signed-off-by: Foxes Hung <foxes687@andestech.com>
> ---
> gdbstub/syscalls.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gdbstub/syscalls.c b/gdbstub/syscalls.c
> index 02e3a8f74c..4c6b5f728b 100644
> --- a/gdbstub/syscalls.c
> +++ b/gdbstub/syscalls.c
> @@ -126,7 +126,7 @@ void gdb_do_syscall(gdb_syscall_complete_cb cb, const char *fmt, ...)
> case 's':
> i64 = va_arg(va, uint64_t);
> i32 = va_arg(va, uint32_t);
> - p += snprintf(p, p_end - p, "%" PRIx64 "/%x" PRIx32, i64, i32);
> + p += snprintf(p, p_end - p, "%" PRIx64 "/%" PRIx32, i64, i32);
> break;
> default:
> bad_format:
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2023-06-20 7:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 9:07 [PATCH qemu 1/2] semihosting: Added to support GDB_O_APPEND flag of host_open() ~foxes
2023-06-08 9:06 ` [PATCH qemu 2/2] gdbstub: Fixed gdb_open() does not work issue while an extra 'x' is being added when converting '%s' to a pointer ~foxes
2023-06-20 7:32 ` Richard Henderson [this message]
2023-06-20 7:30 ` [PATCH qemu 1/2] semihosting: Added to support GDB_O_APPEND flag of host_open() Richard Henderson
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=910efeb9-78c2-659c-3101-0e7dc3770ef5@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=foxes687@andestech.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).