Re: PHP 5 CLI possible bug
| From: | Philip Olson | Date: | Sat, 12 Apr 2003 00:49:03 +0000 |
| Subject: | Re: PHP 5 CLI possible bug | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-143588@lists.php.net to get a copy of this message | ||
On Fri, 11 Apr 2003 janet@valade.com wrote:
> I believe PHP 5 CLI is not working correctly with -a. It comes up correctly
> and tells me it is in interactive mode, but when I enter:
> <?php
> echo "hello";
>
> It crashes. A box comes up that says:
> php.exe has generated errors and will be closed. You need to restart the
> program.
>
> This same procedure works fine with 4.3.0.
>
> I am using Windows 2000. I am using the latest CVS from snaps. build on Apr
> 11 2003 20:08:10 .
>
> I am not sure of the procedure for reporting bugs in PHP 5. Are they supposed
> to be entered in the bugs database, like bugs for php 4? I looked there and
> didn't see any bugs for PHP 5. Perhaps I just don't know how to search the
> database.
The following are labels often used to signify a PHP 5 bug:
Type: Zend Engine 2
Version ex: 5CVS-2003-04-11 (dev)
There are currently bugs that have one or both of these
qualities and search.php allows for these searches. Since
your using Windows I'm not sure how to create a backtrace
but for good measure, here are some steps for reporting
a PHP bug:
a) Is it already a bug? Spend some time searching the
bug database here:
http://bugs.php.net/search.php
b) Follow these detailed instructions on reporting a bug:
How to report a PHP bug:
http://bugs.php.net/how-to-report.php
If a crash / segfault exists, be sure PHP is compiled
with:
--enable-debug
This will help create a useful backtrace. After
compile, create the crash and generate a backtrace:
How to generate a backtrace:
http://bugs.php.net/bugs-generating-backtrace.php
Not sure how to do this in Windows, maybe someone
else does.
c) Report the bug:
http://bugs.php.net/report.php
Be sure to follow the advice in the HOWTO. Like,
include a short example to reproduce the bug and
any other relevent information like for example
if the bug is related to ldap, include ldap version
information.
d) If someone marks it as Bogus don't fret, spend
some time pondering why. Maybe it's not a PHP
bug? Or something silly like a support question?
Or *gasp* a little miscommunication?!
Regards,
Philip