Re: Memory manager fast_cache_list_entry corruption

Got back on my AIX system today; building with --enable-debug eliminates the seg fault. I occasionally receive a message to stdout/stderr from main.c that reads: "Last leak repeated n times...". I am able to sucessfully run all the sample scripts in examples/php with the exception of date.php (missing a CLASSPATH. No big deal I think). Not sure how to interpret the "Last leak..." mesage which happens only intermittantly on various scripts. Bill > The problem is most likely not in the memory manager, but in a piece of > code that uses it. Perhaps the same element is freed twice for some reason > (bug). Did you try building a debug build? Didn't you happen to see > warnings about freeing an already-freed element? > > Zeev > > At 18:24 5/1/2001, Bill Stoddard wrote: > >Running PHP as a servlet under Tomcat on AIX and I am getting a consistent > >segfault on the third call to jver.php. I've debugged to the point of > >identifying a corrupted fast_cache_list_entry. Specifically, while iterating > >through the while loop in shutdown_memory_manager (see below), I hit a > >fast_cache_list_entry whose next pointer points back to itself. efree is > >called multiple times on the same address which eventually results in a seg > >fault. Hoping someone more familier with the code may have some insite on > >where I might look for the bug. > >