On Fri, 25 Feb 2022 at 03:33, wrote:
>
>
> >
> > yes. Could you please send a patch using g_autofree ?
> >
> > Thanks,
> >
> > C.
>
>
> Here is the new patch.
Hi; that patch doesn't seem to be using g_autofree. Did you attach the
wrong version of it?
You've sent a few patches recently, and they
>
> yes. Could you please send a patch using g_autofree ?
>
> Thanks,
>
> C.
Here is the new patch.
Thanks,
WentaoFrom 8ed76446f78ab1b4152403fdb9dd6f349d6fd52e Mon Sep 17 00:00:00 2001
From: Wentao_Liang
Date: Fri, 25 Feb 2022 11:17:33 +0800
Subject: [PATCH] Fix a pot
Hello Wentao,
On 2/23/22 17:15, Philippe Mathieu-Daudé wrote:
On 23/2/22 15:39, wli...@stu.xidian.edu.cn wrote:
Hi all,
I find a memory leak bug in QEMU 6.2.0, which is in
write_boot_rom()(./hw/arm/aspeed.c).
Specifically, at line 276, a memory chunk is allocated with g_new0() and
assigned
On 23/2/22 15:39, wli...@stu.xidian.edu.cn wrote:
Hi all,
I find a memory leak bug in QEMU 6.2.0, which is in
write_boot_rom()(./hw/arm/aspeed.c).
Specifically, at line 276, a memory chunk is allocated with g_new0() and
assigned to the variable 'storage'. However, if the branch takes true at
Hi all,
I find a memory leak bug in QEMU 6.2.0, which is in
write_boot_rom()(./hw/arm/aspeed.c).
Specifically, at line 276, a memory chunk is allocated with g_new0() and
assigned to the variable 'storage'. However, if the branch takes true at line
277, there will be only an error report at lin
