apache PHP segmentation fault

apache PHP segmentation fault

[Sam Edge]

I'm struggling with the PHP Apache module.

	[Tue May  7 16:57:22 2002] [notice] child pid 350 exit signal
	Segmentation fault (11)

I'm getting this diagnostic in /var/log/apache/error_log when I
attempt to serve the basic PHP script test.php;

	<?php phpinfo() ?>

The web browser gets all the phpinfo() output upto the heading for the
"apache" section;

	<h2 align="center"><a name="module_apache">apache</a></h2>
	<table border="0" cellpadding="3" cellspacing="1" width="600"
	bgcolor="#000000" align="center">

I'm using the latest "cur" packages for everything, specifically
apache 1.3.24-4 and mod_php4 4.2.0-1 and can't find anything wrong
with the configuration. The system is Windows NT4.0SP6a.

The fault occurs whether running httpd.exe from the command line using
-X, from the command line with -k, detached from the command line or
as a cygrunsrv NT service. It coredumps and generates an
httpd.exe.stack.dump file in the same directory at test.php.

Is anyone else having the same problem or does anyone have a solution
for this?

Thanks,

-- 
Sam Edge

--
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/

Re: apache PHP segmentation fault

[Sukhwinder Singh]

I think its not cygwin specific error.
go to http://www.geocites.com/honey_jal/index.html#probs and see if you are
using those options mentioned there. I also faced same 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/

Re: apache PHP segmentation fault

[Stipe Tolj]

Sukhwinder Singh wrote:
> 
> I think its not cygwin specific error.
> go to http://www.geocites.com/honey_jal/index.html#probs and see if you are
> using those options mentioned there. I also faced same problems.

I can't reach that URL, maybe a typo?

Stipe

tolj@wapme-systems.de
-------------------------------------------------------------------
Wapme Systems AG

Münsterstr. 248
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: info@wapme-systems.de
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are

--
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/

Re: apache PHP segmentation fault

[Sukhwinder Singh]

>I can't reach that URL, maybe a typo?

yes correct url is. I thing if you are compiling php and yourself and
using --with-swf and/or with-java then this may be causing problems.
http://www.geocities.com/honey_jal/index.htm#prob

--
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/

Re: apache PHP segmentation fault

[Stipe Tolj]

> yes correct url is. I thing if you are compiling php and yourself and
> using --with-swf and/or with-java then this may be causing problems.
> http://www.geocities.com/honey_jal/index.htm#prob

neither of both has been used while building php4.

Stipe

tolj@wapme-systems.de
-------------------------------------------------------------------
Wapme Systems AG

Münsterstr. 248
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: info@wapme-systems.de
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are

--
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/

Re: apache PHP segmentation fault

[Stipe Tolj]

> The fault occurs whether running httpd.exe from the command line using
> -X, from the command line with -k, detached from the command line or
> as a cygrunsrv NT service. It coredumps and generates an
> httpd.exe.stack.dump file in the same directory at test.php.

in general you should avoid to run in -X, because apache's developers
are not any longer worrying about that flag, at least not
significantly.

> Is anyone else having the same problem or does anyone have a solution
> for this?

I haven't seen such effects. Could you please check if the postinstall
script of php did run successfully, it should reside in
/etc/postinstall/php*.

Stipe

tolj@wapme-systems.de
-------------------------------------------------------------------
Wapme Systems AG

Münsterstr. 248
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: info@wapme-systems.de
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are

--
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/

Re: apache PHP segmentation fault

[Sam Edge]

Stipe Tolj wrote in <3CD92533.9B0A0147@wapme-systems.de>
in gmane.os.cygwin on Wed, 08 May 2002 15:16:35 +0200:

> in general you should avoid to run in -X, because apache's developers
> are not any longer worrying about that flag, at least not
> significantly.

I don't in general. Usually I have it running as a cygrunsrv service
with the -k switch. I was just trying to see whether the problem was
related to certain modes of operation. It appears that it isn't.

> I haven't seen such effects. Could you please check if the postinstall
> script of php did run successfully, it should reside in
> /etc/postinstall/php*.

	$ ls /etc/postinstall/*php*
	/etc/postinstall/apache-php.sh.done

/usr/lib/apache/new contains just rebase.exe.
/usr/lib/apache contains libphp4.dll size 1126912 bytes.

/etc/apache/httpd.conf has
	LoadModule php4_module lib/apache/libphp4.dll
after all other LoadModule lines and
	AddModule mod_php4.c
after all other AddModule lines.

I'll try uninstall/reinstall of the PHP package and I'll pay attention
to the postinstall.

-- 
Sam Edge

--
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/

Re: apache PHP segmentation fault

[Sam Edge]

You wrote in <r9didu847jsnm4qhbr3gl87muukivim0e5@4ax.com>
in gmane.os.cygwin on Wed, 08 May 2002 15:51:20 +0100:

> I'll try uninstall/reinstall of the PHP package and I'll pay attention
> to the postinstall.

Well, that didn't help. The postinstall script ran without showing any
errors but the problem is still ocurring when I try to use PHP.

I still can't see anything wrong with the set-up.

-- 
Sam Edge

--
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/

Re: apache PHP segmentation fault

[Stipe Tolj]

Sam Edge wrote:
> 
> Well, that didn't help. The postinstall script ran without showing any
> errors but the problem is still ocurring when I try to use PHP.
> 
> I still can't see anything wrong with the set-up.

Ok, have you set the php4 handler for the .php extensions in
/etc/apache/httpd.conf?

If yes, what exactly happens and when. Is the assigned httpd child
coredumping when you try to access a .php file?

Stipe

tolj@wapme-systems.de
-------------------------------------------------------------------
Wapme Systems AG

Münsterstr. 248
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: info@wapme-systems.de
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are

--
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/

Re: apache PHP segmentation fault

[Sam Edge]

Stipe Tolj wrote in <3CDA53EC.D3866B26@wapme-systems.de>
in gmane.os.cygwin on Thu, 09 May 2002 12:48:12 +0200:

> > Well, that didn't help. The postinstall script ran without showing any
> > errors but the problem is still ocurring when I try to use PHP.
> > I still can't see anything wrong with the set-up.
> Ok, have you set the php4 handler for the .php extensions in
> /etc/apache/httpd.conf?

I've got
	AddType application/x-httpd-php .php
in there but there's no AddHandler line. Should there be?

> If yes, what exactly happens and when. Is the assigned httpd child
> coredumping when you try to access a .php file?

The child process terminates with the error message I've already
mentioned. There's a small stackdump generated in the same directory
as the offending php script but that's all. The web browser gets some
of the output before this happens though. It always gets as far as the
title of the "apache" section to the phpinfo() output and no further.
It behaves exactly the same every time.

I don't have a php.ini file anywhere. From the output of phpinfo()
that I do get this should be in /usr/local/lib/php.ini.

Ah ha! I've copied the php.ini-recommended file from a download of
4.2.0 for Windows native to /usr/local/lib/php.ini and the problem has
gone away. No more segmentation faults.

Perhaps the package should include a default php.ini file for idiots
like me?

Thanks anyway.

-- 
Sam Edge

--
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/

Re: apache PHP segmentation fault

[Sam Edge]

I wrote in <88dldugtt8sfdql1r3inb85uq47frqnuqu@4ax.com>
in gmane.os.cygwin on Thu, 09 May 2002 19:29:59 +0100:

> Ah ha! I've copied the php.ini-recommended file from a download of
> 4.2.0 for Windows native to /usr/local/lib/php.ini and the problem has
> gone away. No more segmentation faults.

I spoke too soon. I've made some small changes in php.ini and the
fault is back but now gets as far as outputing

<h2 align="center"><a name="module_apache">apache</a></h2>
<table border="0" cellpadding="3" cellspacing="1" width="600"
bgcolor="#000000" align="center">
<tr valign="baseline" bgcolor="#cccccc"><td bgcolor="#ccccff"
><b>APACHE_INCLUDE

before the segmentation fault error occurs and the child aborts.

Unfortunately I can't use the simpler part of Sukhwinder Singh's
suggestion because the package isn't compiled with debug enabled.

Perhaps I need to compile my own versions of Apache and mod_php as he
suggests to pin down the location. Ho hum.

Thanks anyway.

-- 
Sam Edge

--
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/

Cygwin/Apache with PHP CGI

[Sam Edge]

Further to my problems with the Apache PHP module package I've given
up for the moment.

Instead I've downloaded the latest 4.2.0 Win32 native PHP ZIP file and
unzipped this into its own directory.

I've then made sure php-cli.exe, sapi\php.exe and php4ts.dll are in my
Windows PATH and copied php.ini-recommended to C:\WINNT\php.ini to get
the command line PHP working.

Finally, to use this from Cygwin/Apache I've commented out the PHP
LoadModule and AddModule lines and created a cgi-bin shell script to
run PHP via an Action line in htppd.conf.

httpd.conf:
	...
	#LoadModule php4_module lib/apache/libphp4.dll
	...
	#AddModule mod_php4.c
	...
	AddType application/x-httpd-php .php
	Action application/x-httpd-php "/cgi-bin/php-cgi"
	...

/var/www/cgi-bin/php-cgi: (or wherever your cgi-bin actually lives)
	#!/bin/sh
	export PATH="/bin:$PATH"
	win_page=`cygpath -w "$PATH_TRANSLATED"`
	export PATH_TRANSLATED="$win_page"
	php 2>&1

The crucial bit is converting PATH_TRANSLATED from Cygwin/Posix format
to Windows native for PHP.EXE to read.

Your PHP script will have to be written with the Windows native filing
system in mind so there are a few other variables that might benefit
from translation too if your script uses them. Cygwin is automatically
translating PATH but DOCUMENT_ROOT and SCRIPT_FILENAME might be needed
too. (Although I can't think why.)

(I appreciate that CGI is a sub-optimal way of using PHP in Apache but
at least this /is/ working for me and allows me to check my code more
easily before uploading to my service provider's Apache/PHP server.)

-- 
Sam Edge

--
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/

Re: Cygwin/Apache with PHP CGI

[Graeme Merrall]

Sam, your mail keeps bouncing. It makes it hard to want to help you when 
you cannot be emailed.

Sam Edge wrote:
> Instead I've downloaded the latest 4.2.0 Win32 native PHP ZIP file and
> unzipped this into its own directory.

I have a patched version of PHP-4.2.0 (actually RC4) for Cygwin you can 
use.
There's is no XML support which is a bit of a stumbling block so if 
anyone can give me a hint as to why I get this error compiling PHP 
against expat-1.95.2 I'd very very appreciative. I know about PHP, not 
compiling against Cygwin :)

dlltool: Syntax error in def file .libs/cygexpat-0.dll-def:0
Warning: resolving _rl_line_buffer by linking to __imp__rl_line_buffer 
(auto-import)
Warning: resolving _rl_point by linking to __imp__rl_point (auto-import)
Warning: resolving _rl_end by linking to __imp__rl_end (auto-import)
Warning: resolving _rl_mark by linking to __imp__rl_mark (auto-import)
Warning: resolving _rl_done by linking to __imp__rl_done (auto-import)
Warning: resolving _rl_pending_input by linking to 
__imp__rl_pending_input (auto
-import)
Warning: resolving _rl_prompt by linking to __imp__rl_prompt (auto-import)
Warning: resolving _rl_terminal_name by linking to 
__imp__rl_terminal_name (auto-import)
Warning: resolving _rl_library_version by linking to 
__imp__rl_library_version (auto-import)
Warning: resolving _rl_readline_name by linking to 
__imp__rl_readline_name (auto-import)
Warning: resolving _rl_attempted_completion_function by linking to 
__imp__rl_attempted_completion_function (auto-import)
Warning: resolving _stdscr by linking to __imp__stdscr (auto-import)
Warning: resolving _COLS by linking to __imp__COLS (auto-import)
./.libs/libphp4.a(xml.o): In function `zm_info_xml':
/home/Administrator/src/php-4.2.0RC4/ext/xml/xml.c:236: undefined 
reference to `_imp__XML_ExpatVersion'
./.libs/libphp4.a(xml.o): In function `xml_parser_dtor':
/home/Administrator/src/php-4.2.0RC4/ext/xml/xml.c:300: undefined 
reference to `_imp__XML_ParserFree'

and so on...

Cheers,
  Graeme


--
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/

Re: Cygwin/Apache with PHP CGI

[Sam Edge]

Graeme Merrall wrote in <3CDB6409.70900@aol.com>
in gmane.os.cygwin on Fri, 10 May 2002 16:09:13 +1000:

> Sam, your mail keeps bouncing. It makes it hard to want to help you when 
> you cannot be emailed.

Odd. My From header is spam-trapped with ZZZ because this is a public
place but your e-mail client should be using Reply-To in preference to
that. Reply-To is set to cygwin@cygwin.com so that it goes to the
mailing list and not just to me.

> I have a patched version of PHP-4.2.0 (actually RC4) for Cygwin you can 
> use.

For the moment I'm happy with the native version. (All I wanted it for
is to be able to test PHP code before sending it to my - pretty basic
- hosting server.)

Thanks anyway.

-- 
Sam Edge

--
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/

Re: apache PHP segmentation fault

[Stipe Tolj]

Sam Edge wrote:
> 
> I've got
>         AddType application/x-httpd-php .php
> in there but there's no AddHandler line. Should there be?

no, AddType is enough. the AddHandler is registed while the module
dynamically links in.
> 
> Ah ha! I've copied the php.ini-recommended file from a download of
> 4.2.0 for Windows native to /usr/local/lib/php.ini and the problem has
> gone away. No more segmentation faults.
> 
> Perhaps the package should include a default php.ini file for idiots
> like me?

yep, definitly for anyone ;)

I'll repackage it and add the default php.ini. Thanks a lot for
pointing this out.

Stipe

tolj@wapme-systems.de
-------------------------------------------------------------------
Wapme Systems AG

Münsterstr. 248
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: info@wapme-systems.de
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are

--
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/

Re: apache PHP segmentation fault

[Sukhwinder Singh]

>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/

Re: apache PHP segmentation fault

[Sukhwinder Singh]

>neither of both has been used while building php4.

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.

But you can try it yourself also.

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.

Follow the steps provided at
http://bugs.php.net/bugs-generating-backtrace.php


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 steps provided at
http://bugs.php.net/bugs-generating-backtrace.php

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/

Re: apache PHP segmentation fault

[Sukhwinder Singh]

>neither of both has been used while building php4.

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.

But you can try it yourself also.

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.

Follow the steps provided at
http://bugs.php.net/bugs-generating-backtrace.php


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 steps provided at
http://bugs.php.net/bugs-generating-backtrace.php

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/

Re: Cygwin/Apache with PHP CGI

[Stipe Tolj]

Sam Edge wrote:
> 
> (I appreciate that CGI is a sub-optimal way of using PHP in Apache but
> at least this /is/ working for me and allows me to check my code more
> easily before uploading to my service provider's Apache/PHP server.)

I wouldn't be to hard this way. At least anything else except the
phpinfo() apache section seem to work very stable from my testings.

So in a development or production area output of phpinfo() won't be of
interest.

I'd like you still to consider using it if possible and we'll check to
make it then work even for the apache module infos.

Stipe

tolj@wapme-systems.de
-------------------------------------------------------------------
Wapme Systems AG

Münsterstr. 248
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: info@wapme-systems.de
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are

--
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/

Re: Cygwin/Apache with PHP CGI

[Sam Edge]

Stipe Tolj wrote in <3CE4ED6B.C5A4C1E2@wapme-systems.de>
in gmane.os.cygwin on Fri, 17 May 2002 13:45:47 +0200:

> I wouldn't be to hard this way. At least anything else except the
> phpinfo() apache section seem to work very stable from my testings.
> So in a development or production area output of phpinfo() won't be of
> interest.
> I'd like you still to consider using it if possible and we'll check to
> make it then work even for the apache module infos.

I've reverted to using the 4.2.0 module. It's still seg-faulting in
phpinfo() but some other simple scripts appear to be working okay.

By the way, PHP 4.2.1 is now available. Would it make sense to port
this to Cygwin first before attempting a debug?

-- 
Sam Edge

--
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/

Re: Cygwin/Apache with PHP CGI

[Stipe Tolj]

Graeme Merrall wrote:
> 
> Sam, your mail keeps bouncing. It makes it hard to want to help you when
> you cannot be emailed.
> 
> Sam Edge wrote:
> > Instead I've downloaded the latest 4.2.0 Win32 native PHP ZIP file and
> > unzipped this into its own directory.
> 
> I have a patched version of PHP-4.2.0 (actually RC4) for Cygwin you can
> use.
> There's is no XML support which is a bit of a stumbling block so if
> anyone can give me a hint as to why I get this error compiling PHP
> against expat-1.95.2 I'd very very appreciative. I know about PHP, not
> compiling against Cygwin :)

yep, expat defines dllimport somewhere for the native Win32 port. This
has to be taken out in a !defined(__CYGWIN__) compile condition style.

Stipe

tolj@wapme-systems.de
-------------------------------------------------------------------
Wapme Systems AG

Münsterstr. 248
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: info@wapme-systems.de
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are

--
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/

Re: apache PHP segmentation fault

[Graeme Merrall]

Sam Edge wrote:
> I'm struggling with the PHP Apache module.
> > I'm using the latest "cur" packages for everything, specifically
> apache 1.3.24-4 and mod_php4 4.2.0-1 and can't find anything wrong
> with the configuration. The system is Windows NT4.0SP6a.
> 

I wasn't aware that a cygwin port of 4.2.0 existed other than I my own 
compiling of the CGI/CLI version of PHP. URL?

> The fault occurs whether running httpd.exe from the command line using
> -X, from the command line with -k, detached from the command line or
> as a cygrunsrv NT service. It coredumps and generates an
> httpd.exe.stack.dump file in the same directory at test.php.
> 
> Is anyone else having the same problem or does anyone have a solution
> for this?

It sounds a lot like an extension is failing to load. Try setting 
display_startup_errors to 'on' in php.ini.
If your version of PHP uses loadable extensions try commenting out the 
extension lines from php.ini and see if the problem goes away.

Cheers,
  Graeme


--
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/