php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #21938 Wrong error line numbers
Submitted: 2003-01-29 05:48 UTC Modified: 2003-02-20 08:04 UTC
Votes:7
Avg. Score:4.7 ± 0.5
Reproduced:7 of 7 (100.0%)
Same Version:2 (28.6%)
Same OS:2 (28.6%)
From: arne dot brachhold at co4 dot de Assigned:
Status: No Feedback Package: Scripting Engine problem
PHP Version: 4.3.1-dev OS: Windows 2000
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: arne dot brachhold at co4 dot de
New email:
PHP Version: OS:

 

 [2003-01-29 05:48 UTC] arne dot brachhold at co4 dot de
The error will be displayed at a wrong line.

Sample:
Undefined variable: foo in foo.php on line 39 

$foo is only used in line 113. This also happends with wrong functions and other errors. This makes it really hard to find errors.

I'm using the windows binary with default configuration. (php.ini-dist).

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2003-01-29 06:02 UTC] sniper@php.net
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.

 [2003-01-29 06:17 UTC] arne dot brachhold at co4 dot de
What I did:
=================

Made a script like this:

<?php

blubb();

?>

What should happen?
========================
This error:

Fatal error: Call to undefined function: blubb() in foo.php on line 3

What happend?
========================
This error:

Fatal error: Call to undefined function: blubb() in foo.php on line 2


As you see the line number is incorrect. It should be 3 instead of 2. As longer the script is as longer are the differences betweeen the correct and displayed line number.
This happens with all errors, warnings ans so on.

this happends since the upgrade of PHP to PHP 4.3.

System: Windows 2000 Server / Apache/1.3.24
Version: PHP 4.3 Windows Binary with unmodified php.ini-dist
 [2003-01-29 07:04 UTC] sniper@php.net
Please try using this CVS snapshot:

  http://snaps.php.net/php4-STABLE-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php4-win32-STABLE-latest.zip

Ilia fixed something like this just few days ago, iirc.

 [2003-01-30 05:41 UTC] arne dot brachhold at co4 dot de
Sorry, this doesn't really help. The numbers are nearer to the right position now, but not correct.

Displayed: ..in Line 125
Correct Position: 138
 [2003-02-04 18:19 UTC] sniper@php.net
Using PHP 4.3.1-dev and running this script:

<?php

   blubb();

?>

What line is the error reported on? (using PHP CLI binary)
And what about with PHP CGI binary ?

For me, it says the error is on line 3, which is correct.
 [2003-02-05 03:45 UTC] arne dot brachhold at co4 dot de
It shows the correct line on short scripts like yours.
But when I create a script, write 20 times

if(isset($blubb)) {


}

ans then blubb(); which is now on line 88, it tells me the error is on line 66. As longer the script is as higher is the difference.

Sorry at the moment i don't have the time to test this with the CGI Binary. But i can do this on weekend.
 [2003-02-13 02:21 UTC] sniper@php.net
What was the result when testing with CGI binary?
(on command line!)

I can't reproduce this with even over 1000 lines of code..

 [2003-02-20 08:04 UTC] sniper@php.net
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.


 [2011-08-23 10:25 UTC] noemail at noemail dot com
This problem occurs when the line breaks are in different format.
Change the line break style to Dos (CR+LF) or Unix (LF) and the problem will 
disapper
 
PHP Copyright © 2001-2022 The PHP Group
All rights reserved.
Last updated: Sun Dec 04 16:05:54 2022 UTC