qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Nikita Shubin" <nikita.shubin@maquefel.me>,
	"Alex Bennée" <alex.bennee@linaro.org>
Cc: Nikita Shubin <n.shubin@yadro.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] gdbstub: Fix SEGFAULT in find_cpu_clusters()
Date: Thu, 14 Sep 2023 14:29:52 +0200	[thread overview]
Message-ID: <96770865-924c-5fe9-48bd-44fa52070ef1@linaro.org> (raw)
In-Reply-To: <20230914122558.2379-1-nikita.shubin@maquefel.me>

Hi Nikita,

On 14/9/23 14:25, Nikita Shubin wrote:
> From: Nikita Shubin <n.shubin@yadro.com>
> 
> target_xml is a dynamic GString, use NULL to initialize it.
> 
> Fixes: 56e534bd11 ("gdbstub: refactor get_feature_xml")
> 
> Signed-off-by: Nikita Shubin <n.shubin@yadro.com>
> ---
> Observed with:
> build-qemu/qemu-system-riscv64 -M sifive_u -bios none -nographic -s
> Segmentation fault
> ---
>   gdbstub/softmmu.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/gdbstub/softmmu.c b/gdbstub/softmmu.c
> index 9f0b8b5497..42645d2220 100644
> --- a/gdbstub/softmmu.c
> +++ b/gdbstub/softmmu.c
> @@ -292,7 +292,7 @@ static int find_cpu_clusters(Object *child, void *opaque)
>           assert(cluster->cluster_id != UINT32_MAX);
>           process->pid = cluster->cluster_id + 1;
>           process->attached = false;
> -        process->target_xml[0] = '\0';
> +        process->target_xml = NULL;

Yes, good catch. Akihiko also posted the same fix 2 days ago:
https://lore.kernel.org/qemu-devel/20230912065811.27796-2-akihiko.odaki@daynix.com/

>   
>           return 0;
>       }




      reply	other threads:[~2023-09-14 12:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-14 12:25 [PATCH] gdbstub: Fix SEGFAULT in find_cpu_clusters() Nikita Shubin
2023-09-14 12:29 ` Philippe Mathieu-Daudé [this message]

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=96770865-924c-5fe9-48bd-44fa52070ef1@linaro.org \
    --to=philmd@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=n.shubin@yadro.com \
    --cc=nikita.shubin@maquefel.me \
    --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).