#23135 [Opn->Fbk]: PHP Outputs Wrong Error Line Numbers
| From: | sniper@php.net | Date: | Wed, 09 Apr 2003 21:56:56 +0000 |
| Subject: | #23135 [Opn->Fbk]: PHP Outputs Wrong Error Line Numbers | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-37493@lists.php.net to get a copy of this message | ||
ID: 23135
Updated by: sniper@php.net
Reported By: duerra at yahoo dot com
-Status: Open
+Status: Feedback
Bug Type: Scripting Engine problem
Operating System: XP Pro
PHP Version: 4.3.1
New Comment:
Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php
If you can provide more information, feel free to add it
to this bug and change the status back to "Open".
Thank you for your interest in PHP.
,
Previous Comments:
------------------------------------------------------------------------
[2003-04-09 10:30:00] duerra at yahoo dot com
Greetings. The original Bug Report for this was posted here:
http://bugs.php.net/bug.php?id=21938
However, the topic is now closed.
I too am experiencing this issue. Here's the breakdown:
Problem: When there is an error in one of your scripts, such as a
missing semi-colon, PHP outputs the error on the page as a completely
wrong line number. The only consistency in this bug that I can find is
that PHP seems to always report that this error is on an EARLIER line
number than it actually is.
Example:
//line 145
echo "something something something"
//continue...
PHP would report the error as occuring on line, say, 130, for example.
The only real breakdown I can come up with here is that it *seems* to
only occur on my larger scripts. One script that I know has the
problem is required_once() in almost all my other scripts, but these
scripts do not *necissarily* inherit the problem, though they might.
PHP 4.3.1
XP Pro
Apache 2
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=23135&edit=1