From: Steve L. <st...@si...> - 2001-02-12 23:31:22
|
On Mon, 12 Feb 2001, Chris Nandor wrote: > >- Should I need to re-make slash following the server rebuild? I haven't > >so far, because I couldn't see how it would be related to the apache > >build. > > You should not need to, but I do wonder if you might have some modules not > in the right place, or maybe have the old Slash.pm lying around somewhere. I did find a couple of old Slash.pm's around, although I don't think they were in any path that could have conflicted. I renamed them just in case, but the crash still happens. Should I remove the directory containing my old slash 1.0.9 install? (I'd prefer not to if it's not necessary.) I did an strace of Apache crashing with the slash startup enabled; I'm venturing into unknown territory for myself here. It's monstrously long; the last thing that happens before the segfault is this: read(4, "##\n## access.conf -- Apache HTTP"..., 4096) = 348 read(4, "", 4096) = 0 close(4) = 0 munmap(0x402b3000, 4096) = 0 --- SIGSEGV (Segmentation fault) --- +++ killed by SIGSEGV +++ I posted the whole transcript (about 300k), in case anyone has a second to peek at it and is feeling charitble, at: <http://silicongoblin.com/apache-strace.txt> (or a 39k gzip version at <http://silicongoblin.com/apache-strace.gz>) Finally, I followed the apache recipe at <http://www.delouw.ch/linux/apache.phtml> pretty closely, adding PERL_MARK_WHERE=1 to the mod_perl configuration as per the Slash install instructions. I did this for Slash 1.0.9 as well and it worked fine. I'm pretty stuck at this point; any suggestions would be very, very welcome. I want to start writing some tutorial documentation as well, or at least seed some with answers to my own FAQs. Any clues that help me progress will go in, of course. Cheers! -- Steve Linberg, Chief Goblin Silicon Goblin Technologies http://silicongoblin.com Be kind. Remember, everyone you meet is fighting a hard battle. |