[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <dacaa7f4ec6db4a3f3634368001f0bd9@smtp.hushmail.com>
Date: Sun, 9 Jun 2013 20:41:13 +0200
From: magnum <john.magnum@...hmail.com>
To: "john-dev@...ts.openwall.com" <john-dev@...ts.openwall.com>
Subject: Confusing output from memdbg
Jim,
I tried turning memdbg on and run --test=0
For CPU and CUDA formats, all is fine. But for OpenCL I get this output for all but the first format: "Mem leak: nnnn bytes, alloc_num nn, file common-opencl.c, line 1267"
This is the corresponding code:
1266 MEM_FREE(kernel_source);
1267 kernel_source = mem_calloc(source_size + 1);
How can that be a memory leak? I put some printf's in to verify that before line 1266, the old pointer is intact so that buffer is freed in line 1266. I also verified the pointer is reset to NULL after line 1266. So why does it think it's a memory leak?
magnum
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
