On Fri, Jun 19, 2009 at 09:21:47PM +0700, "Denis F. Latypoff"
<de...@gostats.ru> wrote:
>
> More proper patch is attached.
The patch still breaks libev and that is still not a memleak in libev.
Refer to the mailing list archives and the documentation for the reasons
why.
In short, your mistake is to misinterpret valgrind output as a memleak (it
isn't, read closely what it actually says).
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / p...@goof.com
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
libev mailing list
libev@lists.schmorp.de
http://lists.schmorp.de/cgi-bin/mailman/listinfo/libev
