On Fri, Nov 2, 2007 at 11:59 AM, Dan Kegel <[EMAIL PROTECTED]> wrote:
> Here are the directories that still have warnings:
>
> advapi32 advpack cabinet comctl32 crypt32 d3d8 d3d9 d3dx8
> dplayx dsound gdi32 gdiplus hlink kernel32 mlang msacm32
> mscms mshtml msi msvcrt msxml3 netapi32 ntdll ole32
>
Am Freitag, 2. November 2007 22:10:28 schrieb Dan Kegel:
> On 11/2/07, Dan Kegel <[EMAIL PROTECTED]> wrote:
> > Online at http://kegel.com/wine/valgrind/20071002/
>
> I should mention: I'm not planning fixing any of these
> myself for now (I'd love to, but I can't afford to type that
> much).
> I'm
On Friday 02 November 2007 19:59:10 Dan Kegel wrote:
> dplayx
I'm not sure if this is worth the effort right now. It seems to be leaking
some memory, but everybody _using_ dplay with wine right now uses native,
anyway.
> netapi32
That's my fault, working on it.
Cheers,
Kai
--
Kai Blin
World
On 11/2/07, Dan Kegel <[EMAIL PROTECTED]> wrote:
> Online at http://kegel.com/wine/valgrind/20071002/
I should mention: I'm not planning fixing any of these
myself for now (I'd love to, but I can't afford to type that
much).
I'm hoping other Wine developers will pitch in to clean the
real valgrind
Online at http://kegel.com/wine/valgrind/20071002/
(I now include more info about memory leaks, but I still
only report anything if there was an invalid memory reference.)
The following tests were fixed in git yesterday, and no longer have
any valgrind warnings:
comctl32/rebar
comctl32/status
cryp
