On Thu, Jun 19, 2008 at 01:22:20PM -0700, Michael Leib <[EMAIL PROTECTED]>
wrote:
> working as I have found what I belive is a memory leak in libev when dealing
> with signals and the deafult loop.
It's not a leak, search the list archives for details if you are intersted.
> 1) The "signals" array is never freed
So is your code section and your data section. Are these leaks? No...
> 2) Pending signal events are not restored to to system default handling when
> the default loop is destroyed.
Yes, signals are only reported to the default loop, but they are a
process-global resource.
> I hope this e-mail brings out a shortcoming and provides a solution. I would
> not have caught this without duma.
Careful reading of the libev docs or looking at the list archives would have
helped as well.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED]
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
libev mailing list
libev@lists.schmorp.de
http://lists.schmorp.de/cgi-bin/mailman/listinfo/libev
