|
From: | Paul Brook |
Subject: | Re: [Qemu-devel] [PATCH 04/17] virtio-9p: Implement P9_TSTAT |
Date: | Tue, 9 Mar 2010 12:30:08 +0000 |
User-agent: | KMail/1.12.4 (Linux/2.6.32-trunk-amd64; KDE/4.3.4; x86_64; ; ) |
> Is there any reason (other than being coding style) in using qemu_free() > instead of free()? As per qem-malloc.c qemu_free() is nothing but free(). The whole point of qemu_{malloc,free} is to isolate code from the system implementation of malloc/free. It's entirely possible that future versions of qemu_malloc will use a different memory allocation strategy. > The reason I am asking is.. tracking string allocs become tricky > if some of them were defined using qemu_alloc() and others are allocated > through sprintf(). sprintf does not allocate memory. If you mean strdup, then you shouldn't be using that (use qemu_strdup). Paul
[Prev in Thread] | Current Thread | [Next in Thread] |