Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I'm using a rather complex structure with multiple ssi-includes, set- and echo-commands.

The first document writes a lot of set-commands, includes another document which then again includes a third document. On the last included document the variable values are printed using the echo-command.

I noticed that with an increasing number of variables the probability for a segmentation fault to happen rises.

Did anyone experience something similar? How do I go about debugging such a problem?

I'm using IBM_HTTP_Server/2.0.47.1-PK65782 Apache/2.0.47

share|improve this question

2 Answers 2

Generally speaking Apache should never segmentation fault. I would use a test server and turn on all logging, and also peek into the process with strace to see where it is segfaulting at.

If you are sure it is mod_include, make sure it is compiled with the same version of apache you are running - if it was compiled for a different version that could explain the segfaults.

share|improve this answer

If it segfaults, you should be able to retrieve a core dump that will help to understand what happened at code level. Consult your operating system documentation to figure out how to collect the dump. Once you have it, you can examine the full internal state of the process at the time of the crash using your favourite debugger.

Strace doesn't help much with segfaults as it will only tell you what happens between userland and kernel while the segfault is usually indicative of a purely userland issue. If you are running Linux, valgrind and ltrace are more appropriate in this case. But first, get a backtrace out of the core.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.