Yes, I've just taked in account that it happens at clean-up time, at perl shutdown. So I suppose that's nothing wrong with this. Don't know why, I supposed it was related to the GTopLimit automatic server kill. Now I see that it can be true.
My intention was to try to find out if this coredumps where related to the sudden change of UTF8 codification, which is the main problem I have now. Once this happens the only solution is to reboot the entire machine. Some Segfault like that can lead to a glibc or iconv library corruption? The fact that a reboot is needed makes me suspect that glibc is involved. It's right this assumption? Many thanks again. On dl, 2004-11-08 at 15:48, David Hodgkinson wrote: > On 8 Nov 2004, at 14:39, Marc Gracia wrote: > >> So, my question is... There is any way to force apache to dump a > >> coredump file? I suppose I'm forgotting something but I really > >> desperate... > > Yes. > > As root, you need to do the ulimit magic and then start the server. > > My question is: do you *really* need to debug this? For sure, the > process > has got its knickers in a twist, but this is happening at cleanup time > anyway and not during any request. > > I'm sure you have better things to worry about. > > Cheers, > > Dave > -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
