At Mon, 28 Oct 2002 17:09:32 +0000, Tony Hoyle wrote: > > Original reporter, Tony, please tell us whether your report is really > > same bug #165699, #165718, and #165719, or not. If it seems to be same > > (I also think), and #165699-#165719 is fixed, then I close this bug. > > > Not sure. Only Apache is broken, and if I downgrade libc6 I have to > downgrade a lot of other packages that depend on it, which is a real > pain (I have an 80% working system so far but haven't tracked down all > the dependencies yet).
So, it's still vague that glibc or apache has a problem. We want the evidence: it's a bug or not. > I figured Apache just needed a recompile to work, which is why I filed > the bug. > > From the looks of it this is *not* the same bug - does not die in > strcmp (#165699), does not run up far enough to actually produce any > output in the error/access logs (#165719). On testing it does appear to > be php4 related though - php4 starts mallocing lots of 16 byte blocks of > memory then segfaults. > > This is definately with 2.3.1-3 so is not fixed with that version. I > have to downgrade to 2.2.5-15 before I can start apache (removing php is > not an option). If only recompilation resolve this problem, could I reassign this bug to apache? Regards, -- gotom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
