Re: [PATCH 0/7] hw/riscv: fix leak, add more g_autofree

On Tue, Jan 23, 2024 at 9:39 AM Daniel Henrique Barboza wrote: > > Hi, > > First patch fixes a leak found when using Valgrind. The root cause is a > missing g_free() in a string. > > In fact, I found while doing reviews that we keep repeating the same > pattern: > > > char *name; > name = g_s

[PATCH 0/7] hw/riscv: fix leak, add more g_autofree

Hi, First patch fixes a leak found when using Valgrind. The root cause is a missing g_free() in a string. In fact, I found while doing reviews that we keep repeating the same pattern: char *name; name = g_strdup_printf(...); (...) g_free(name); With this in mind, I ended up making th