hi,
i know. the problem is i have used the thttpd sapi module as a sample and it
is supposed to be stable. i have solved my problem by using plain
malloc/free - my reason to share this experience is that there may be a leak
or segfault in some of the sapi modules. i haven't found neighter bug nor
leak still but it is possible.
can someone tell me the exact places where emalloced memory begins to be
tracked and where the leaks are efreed?
b.
> BB>> i have hit on this issue while trying to make a sapi module. my
> BB>> problem was that memory emalloc-ed _before_ the request got
> BB>> efree-ed by the memory manager after the request and when i
> BB>> efree it afterwards a total memory mess occurs (sigsegv,
> BB>> infinite loop in libc free or something more nasty)...
>
> You probably should use plain old malloc when you not inside the request.
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
