At Mon, 28 Oct 2002 09:48:49 -0700, Adam Conrad wrote: > > So, I wonder they're really same bugs. But it seems that other php4 > > issue seems being fixed in 2.3.1-3, so this #166414 bug should be > > already fixed. > > The bugs are still there, AFAICT. It does appear that some people (You, > Steve Langasek) can't reproduce this, while others (me, submitters, > several people who've mailed me privately about it) get the segv on > every apache invocation. Here's a full backtrace of "/usr/sbin/apache > -X":
Hmm... I also check but this route works in my environment. But the important point of this backtrace is "libc is crashed at strcmp(), and libc is only related with strcmp()". I doubt that OBJ_NAME_new_index() passes an invalid pointer to strcmp() in libcrypto.so.0.9.6. Please, please hunt the condition with "minimal configuration data" and "core with gdb". I don't acknowledge it's glibc bug from this data. Regards, -- gotom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

