ID:               37188
 User updated by:  phpclub_ru at bougakov dot com
 Reported By:      phpclub_ru at bougakov dot com
-Status:           Feedback
+Status:           Open
 Bug Type:         Reproducible crash
 Operating System: Windows XP Home, SP2
 PHP Version:      4.4.2
 New Comment:

STOP POSTING AUTOMATED REPLIES JUST FOR CHANGING BUGs STATUS FROM
'open', WITHOUT CARING TO READ IT FIRST!

I can not generate backtrace:
- the debug build from emini.dk is broken - it simply doesn't work
- the source package from php.net (latest .bz2 file for version 4.4.2)
doesn't compile - it breaks on

c:\php\php-4.4.2\ext\pcre\pcrelib\pcre_internal.h(219) : fatal error
C1189: #error :  LINK_SIZE must be either 2, 3, or 4

Anyway the bug reproduces on two different machines with official PHP
4.4.2 binary from your website.

Don't want to check it out for yourselves with the official binaries
("my version from some cvs works" is not the answer)? Then give me the
sources that will compile, or compiled binary that actually runs.


Previous Comments:
------------------------------------------------------------------------

[2006-04-29 11:44:53] [EMAIL PROTECTED]

Thank you for this bug report. To properly diagnose the problem, we
need a backtrace to see what is happening behind the scenes. To
find out how to generate a backtrace, please read
http://bugs.php.net/bugs-generating-backtrace.php for *NIX and
http://bugs.php.net/bugs-generating-backtrace-win32.php for Win32

Once you have generated a backtrace, please submit it to this bug
report and change the status back to "Open". Thank you for helping
us make PHP better.



------------------------------------------------------------------------

[2006-04-27 18:56:50] phpclub_ru at bougakov dot com

edink,

seems like something wrong is with your debug build. When I am trying
to make supplied php.exe to parse any PHP script (including trivial
"phpinfo") I always get the same: 

  c:\Downloads\php debug>php -e -n -f php_test.php
  No input file specified.

No matter how I launch it: using Apache, or directly from command line.


Are you sure everything is OK with your build?

------------------------------------------------------------------------

[2006-04-25 12:27:32] [EMAIL PROTECTED]

I cannot reproduce this with debug build. You can test it yourself with
this build:

http://php.emini.dk/misc/php-4.4.3-dev-Win32-debug.zip


------------------------------------------------------------------------

[2006-04-25 09:42:46] phpclub_ru at bougakov dot com

> Please use snapshots instead of homemade builds

There is NO debug pack for Windows version of PHP 4.4.x on
http://snaps.php.net/ (only for 5.1.x-dev)

> To properly diagnose the problem, we
> need a short but complete example script 

1. Obtain PHP 4.4.2 for Windows from http://www.php.net/downloads.php
2. Edit php.ini: replace default 
include_path = ".;c:/php/includes/" with
include_path =   "c:/php/includes/"
3. Open test.php in browser containing
<?php 
  include '/whatever.php';
?>
4. Wait for the nice "Unhandled exception at 0x7c910f2b in php.exe"
window to appear.

------------------------------------------------------------------------

[2006-04-25 08:49:40] [EMAIL PROTECTED]

>Can't build debug version of PHP since there is some error in the
sources 
>(compiler breaks when processes regex-related files and generates
about 18 errors). 

There is absolutely no need to build PHP yourself.
The process of getting a backtrace is described here:
http://bugs.php.net/bugs-generating-backtrace-win32.php

Please use snapshots instead of homemade builds, as we do not support
unofficial win32 builds.

>If YOU have got debug version of PHP 4.4.2, you can easily
> reproduce the bug by editing your php.ini:

No Windows$ here.
And I cannot reproduce it on Linux:

Warning: main(test1.php): failed to open stream: No such file or
directory in 
Warning: main(): Failed opening 'test1.php' for inclusion
(include_path='&#1088;&#1091;&#1089;&#1089;&#1082;&#1080;&#1077;
&#1089;&#1080;&#1084;&#1074;&#1086;&#1083;&#1099;') 


------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/37188

-- 
Edit this bug report at http://bugs.php.net/?id=37188&edit=1

Reply via email to