Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-Originating-IP:	[203.90.98.131]
Reply-To:	"Sukhwinder Singh" <ssruprai AT hotmail DOT com>
From:	"Sukhwinder Singh" <ssruprai AT hotmail DOT com>
To:	"Stipe Tolj" <tolj AT wapme-systems DOT de>
Cc:	<cygwin AT cygwin DOT com>
References:	<01ufduo7c330fgmratp0qgfrgqkdv7upa8 AT 4ax DOT com> <3CD92533 DOT 9B0A0147 AT wapme-systems DOT de> <r9didu847jsnm4qhbr3gl87muukivim0e5 AT 4ax DOT com> <71hidu8lr0qssqnne37377r6aac6t40l8n AT 4ax DOT com> <3CDA53EC DOT D3866B26 AT wapme-systems DOT de>
Subject:	Re: apache PHP segmentation fault
Date:	Fri, 10 May 2002 14:45:29 +0530
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
Message-ID:	<OE15A9FlGn8FfWHcavH0000ae50@hotmail.com>
X-OriginalArrivalTime:	09 May 2002 21:35:29.0439 (UTC) FILETIME=[709FA2F0:01C1F7A1]

>neither of both has been used while building php4.

I don't know about cygwin but I think that it is not cygwin specific error
because I faced same problems after compiling php 4.2 and apache 2.0 on
Linux. Problems were with java and swf extensions.

I think person who has compiled this php module will be in a better position
to find the cause of this fault.

If you know that php module was compiled with --enable-debug option and want
to try yourself, then gdb (GNU debugger) can be used to find the cause.

$ gdb /usr/local/bin/httpd

replace path with your own httpd path

gdb> run -X

Now using second terminal try to access any php page which is causing this
segmentation fault. Now on the first terminal you will see some errors etc.
are displayed. To generate backtrace type:

gdb> bt

This will generate backtrace and will show which extension etc. (c file) is
causing problems. Submit this backtrace to the person who has ported this
module.

If debugging wasn't enabled when compiling php then do you know support for
which extensions is enabled (extensions enabled using --with-xxx options
when compiling php). If you know then list them and I'll try to compile php
using those extensions and see if this also causes problems on Linux.

Other option is to try to compile php and apache yourself using cygwin. The
earlier link http://www.geocities.com/honey_jal/index.htm provides
information about how to compile php and apache on Linux. I think same
procedure may be followed when compiling using cygwin.

If you want to compile php and apache yourself to see what is causing
problems then you can do this:

First try to compile php without enabling any extension. If everything
works, then it is possible that some extension is causing this problem.

Then compile php again with options you want to use but this time also
use --enable-debug option. Now follow the same procedure as above.

Now to find what is causing segmentation fault you have to use gnu debugger
(gdb).

If debugging is enabled (using --enable-debug) gdb can be used:

$ gdb /usr/local/bin/httpd

replace path with your own httpd path

gdb> run -X

Now using second terminal try to access any php page which is causing this
segmentation fault. Now on the first terminal you will see some errors etc.
are displayed. To generate backtrace type:

gdb> bt

This will generate backtrace and will show which extension etc. (c file) is
causing problems.

Sukhwinder Singh

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -