Re: [PATCH] block: Free iovec arrays allocated by multiwrite_merge()

[Avi Kivity <avi@redhat.com>]

On 04/25/2010 04:27 PM, Stefan Hajnoczi wrote:
> From: Stefan Hajnoczi<stefanha@gmail.com>
>
> The MALLOC_TRACE output didn't look useful when I tried it either.
>
> Instead I used the following to find origin of the leak.  Still very basic but
> works better with qemu_malloc() and friends.
>
> This is just a hack but I wanted to share it in case someone finds it useful in
> the future.
>
> new file mode 100644
> index 0000000..a5fa51a
> --- /dev/null
> +++ b/leakcheck.c
> @@ -0,0 +1,17 @@
> +#include<stdio.h>
> +
> +static FILE *fp;
> +
> +extern void leakcheck_log(char action, void *old_addr, void *addr, size_t size, void *ret1);
> +
> +void leakcheck_log(char action, void *old_addr, void *addr, size_t size, void *ret1)
> +{
> +	if (!fp) {
> +		fp = fopen("/tmp/leakcheck.log", "w");
> +		if (!fp) {
> +			return;
> +		}
> +	}
>    

use backtrace(3) or backtrace_symbols(3), or even better, an external tool?

-- 
error compiling committee.c: too many arguments to function