-- Here's a forwarded copy of a bug report that was sent to me by one of my co-workers here at Brodia: >There seems to really be a bug. Basically the initialization routine >sets up a memory pool for the jserv functions to use, but before it does >that, it runs some other stuff that does things with the pool if the >pool is >initialized (which it isn't). Then the httpd for reasons I don't >understand >runs some cleanup and then runs the init functions again. The cleanup >among other things destroys all the memory pools, which is ok because >the init functions should re-allocate them. However, the old pointer to >the >jserv pool is still around, so the code in the jserv init function that >runs before >allocating the pool, the second time it runs, now thinks the jserv pool >is already >initialized when in fact it points to freed memory containing garbage, >so it crashes. > -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] READ THE FAQ!!!! <http://java.apache.org/faq/> Archives and Other: <http://java.apache.org/main/mail.html/> Problems?: [EMAIL PROTECTED]
