Parse errors not shown?

[DaneEveritt]

I can't seem to get Tracy to handle Syntax/Parse errors on my server, is there something I am missing?

I am using the code below, it catches Exceptions, but not Syntax errors for some reason.

use Tracy\Debugger;
Debugger::enable(Debugger::DEVELOPMENT, dirname(__DIR__).'/logs');
Debugger::$strictMode = TRUE;

[dg]

Is syntax error in file, where is also Debugger::enable()?

[DaneEveritt]

The syntax error is in a different file, but the debugger code is included on the pages.

[dg]

The point is: are you sure that Debugger::enable() is called?

[DaneEveritt]

Yeah, the code is here: https://github.com/DaneEveritt/PufferPanel/blob/master/src/framework/framework.core.php#L40

It works fine if an exception is thrown, but for syntax errors and stuff it doesn't do anything.

[JanTvrdik]

@DaneEveritt The problem is that you include framework.core.php (which contains Debugger::enable()) from a file which contains a syntax error, therefore the file is never executed, therefore the include is never executed and finally therefore Debugger::enable() is not called.

[DaneEveritt]

@JanTvrdik I tried to get tracy to work correctly with an error, this is the code from my test file:

<?php 

require_once('../vendor/autoload.php');

use Tracy\Debugger;
Debugger::enable(Debugger::DETECT);
Debugger::$strictMode = TRUE;


echo "hello"
echo "something else"
?>

This error was thrown:

[06-May-2014 12:04:37 America/New_York] PHP Parse error:  syntax error, unexpected 'echo' (T_ECHO), expecting ',' or ';' in test.php on line 11

However, tracy did not display any error page or do anything.

[dg]

Again:

• file contains a syntax error
• therefore the file is never executed
• therefore Debugger::enable() is not called

Tracy shows parse errors, but in your example Tracy was not enabled.

[DaneEveritt]

Oh I understand now, sorry about that.

So if I include a file with a syntax error into a file that has tracy enabled it will work, just not the other way around.

[fprochazka]

@DaneEveritt exactly.

[DaneEveritt]

Time to figure out how to implement this in a way that can catch those in my code then. At least it works fine for exceptions which are the bigger problem, syntax errors don't usually make it past local development.

[dg]

Try to run Tracy as soon as possible, in first script.

[DaneEveritt]

The problem is that the way I am running it won't catch the syntax errors because I included it in the core file which is then included on all the pages. Based on the above responses I would need to be including all of the pages onto the core file for it to catch the errors, which isn't feasible.