php-windows Digest 13 Feb 2009 06:02:39 -0000 Issue 3574
Topics (messages 29179 through 29181):
Re: Access Violation
29179 by: Herb Munson
29180 by: Ruslan Yakushev
XDEBUG with 5.2.6, IIS 5.1, CGI
29181 by: Herb Munson
Administrivia:
To subscribe to the digest, e-mail:
php-windows-digest-subscr...@lists.php.net
To unsubscribe from the digest, e-mail:
php-windows-digest-unsubscr...@lists.php.net
To post to the list, e-mail:
php-wind...@lists.php.net
----------------------------------------------------------------------
--- Begin Message ---
It is on a development machine, and performance is not an issue (well, it
sort of is an issue: php should <run>.) So I guess I'll go to cgi.
As I recall, the MS site to download fastcgi states pretty clearly what it
is intended to run on, and IIS 5.1 is not there - even though the MS links
<pointing> to that download say fastcgi is available for 5.1. Coward that I
am, I did not try it. So I appreciate the clarification that it does indeed
work with 5.1.
Many thanks. I look forward to this being fun again...
Herb
-----Original Message-----
From: Elizabeth M Smith [mailto:auroraeosr...@gmail.com]
Sent: Wednesday, February 11, 2009 5:40 PM
To: php-wind...@lists.php.net
Subject: Re: [PHP-WIN] Access Violation
Louis Solomon [SteelBytes] wrote:
> forget the ISAPI, use FastCGI. In my experience the ISAPI has never
> been stable or working fully.
>
> mmm, not sure FastCGI is available for IIS for XP, so since it's
> probably only a dev machine go to just php as cgi. that works fine on
> all OSes
>
> Louis
>
Yes, you'll have much better luck with fastcgi - and yes the fastcgi
stuff works on IIS 5.1 which ships with XP (just use the IIS 6.0
installer for fastcgi from iis.net)
Have fun,
Elizabeth
--- End Message ---
--- Begin Message ---
FastCGI extension does work with 5.1. Up until last month the EULA in the
installer said that it was supported for IIS 6.0 only, but in fact it also
worked on 5.1. Last month the license has been updated so now the FastCGI
extension is officially supported for IIS 5.1.
-----Original Message-----
From: Herb Munson [mailto:herbmun...@q.com]
Sent: Thursday, February 12, 2009 9:22 AM
To: 'Elizabeth M Smith'; php-wind...@lists.php.net
Subject: RE: [PHP-WIN] Access Violation
It is on a development machine, and performance is not an issue (well, it
sort of is an issue: php should <run>.) So I guess I'll go to cgi.
As I recall, the MS site to download fastcgi states pretty clearly what it
is intended to run on, and IIS 5.1 is not there - even though the MS links
<pointing> to that download say fastcgi is available for 5.1. Coward that I
am, I did not try it. So I appreciate the clarification that it does indeed
work with 5.1.
Many thanks. I look forward to this being fun again...
Herb
-----Original Message-----
From: Elizabeth M Smith [mailto:auroraeosr...@gmail.com]
Sent: Wednesday, February 11, 2009 5:40 PM
To: php-wind...@lists.php.net
Subject: Re: [PHP-WIN] Access Violation
Louis Solomon [SteelBytes] wrote:
> forget the ISAPI, use FastCGI. In my experience the ISAPI has never
> been stable or working fully.
>
> mmm, not sure FastCGI is available for IIS for XP, so since it's
> probably only a dev machine go to just php as cgi. that works fine on
> all OSes
>
> Louis
>
Yes, you'll have much better luck with fastcgi - and yes the fastcgi
stuff works on IIS 5.1 which ships with XP (just use the IIS 6.0
installer for fastcgi from iis.net)
Have fun,
Elizabeth
--- End Message ---
--- Begin Message ---
Well, I'm now set up with CGI on my XP - IIS 5.1 - PHP 5.2.6 system. And
its much more fun now, it doesn't seem to be kicking off all those Access
Violations, as isapi did. Many thanks for that.
But now where xdebug worked (on those rare occasions without access
violations) - nada. NetBeans tries to load xdebug, and tries and tries, and
nothing good happens (it doesn't connect).
I'm using php_xdebug-2.0.4-5.2.8-nts.dll, corresponding to the download link
"5.2 VC6 Non-thread-safe". Looks right to me, but what do I know. (Yup, the
ini file points to this replacement for the ts version I used before, and
the 4 xdebug parameters are set.) If the dll isn't the problem, there
doesn't seem to be much more that could be wrong. So simple, yet I've
screwed it up.
Any suggestions? It would REALLY be nice to have a debugger. Banging my
head against the wall is starting to hurt quite a bit.
--- End Message ---
