On Thu, 19 Jul 2007 19:44:37 +0200 (CEST), "Derick Rethans"
<derick[@]xdebug.org> said:
> On Thu, 19 Jul 2007, Eliteforce wrote:
>
> > On Thu, 19 Jul 2007 10:26:24 +0200 (CEST), "Derick Rethans"
> > <derick[@]xdebug.org> said:
> > > On Thu, 19 Jul 2007, Eliteforce wrote:
> > >
> > > > i'm new to xdebug and i'm having difficulties getting it to work with
> > > > scripts run from command line.
> > > >
> > > > php.exe -v
> > > > PHP 5.2.3 (cli) (built: May 31 2007 09:37:22)
> > > >
> > > > xdebug:
> > > > php_xdebug-2.0.0-5.2.2.dll
> > > >
> > > > to load xdebug i added the following line to php.ini
> > > > zend_extension_ts="C:\path\to\php\php_xdebug.dll"
> > > >
> > > > now if i run a script with php.exe there is no error output although
> > > > there are compilation errors,
> > >
> > > 1. make sure you have display_errors on, and
> > > 2. show me your "php -v" and "php -i" outputs.
> >
> > ohhoho, enabling display_errors gives me the desired output
> > i also enabled to display startup errors
> >
> > i think this should be mentioned in the documentation (installation
> > section)
>
> Why? Xdebug does not behave differently on *when* it shows error
> message. It follows all the standard PHP settings such as
> display_errors, html_errors and error_reporting.
>
> regards,
> Derick
but it suppresses e.g. parse errors when display_errors = Off, whereas
php without
the xdebug extension loaded prints those errors to stderr (i guess) no
matter if
display_errors = On | Off.
that's what confused me..
cheers,
eliteforce
-- http://www.fastmail.fm - Does exactly what it says on the tinReceived on Thu Jul 19 2007 - 21:05:46 BST
This archive was generated by hypermail 2.2.0 : Mon Jun 25 2018 - 06:00:04 BST