At Mon, 28 Oct 2002 09:48:49 -0700, Adam Conrad wrote: > 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": > > Program received signal SIGSEGV, Segmentation fault. > 0x0fd6cef0 in strcmp () from /lib/libc.so.6 > (gdb) bt > #0 0x0fd6cef0 in strcmp () from /lib/libc.so.6 > #1 0x0f743488 in OBJ_NAME_new_index () from /usr/lib/libcrypto.so.0.9.6
I notice that you use "/usr/lib/libcrypto.so.0.9.6", but in my machine it uses "/usr/lib/i686/libcrypto.so.0.9.6". libssl has architecture optimization package, is it possibly related issue? > #5 0x0f1227f4 in SSL_library_init () from /usr/lib/libssl.so.0.9.6 It also uses "/usr/lib/i686/libssl.so.0.9.6" instead of your normal ssl. Why does your system choose /usr/lib/, not /usr/lib/i686/ ? In addition, my machine is Athlon. Regards, -- gotom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
