[xdebug-general] Re: xdebug doesn't connect to debugger

From: Vijay Ramachandran <vijaysr[@]yahoo-inc.com>
Date: Tue, 9 Jul 2013 13:39:25 +0530

On 07/09/2013 12:30 PM, Derick Rethans wrote:
> On Wed, 3 Jul 2013, Vijay Ramachandran wrote:
>
>> On 07/03/2013 01:53 PM, Derick Rethans wrote:
>>> I would suggest to have a look at the /tmp/xdebug.log contents, as it
>>> might provide valuable clues.
>> Thanks for your reply. There is nothing in /tmp/xdebug.log - which makes me
>> think that xdebug doesn't try to connect to the debug client. The only
>> information is a stack trace in the apache logs.
> Which stack trace is that?
>

Every request seems to produces a call stack trace in the apache error
log when an error occurs (xdebug.default_enable is set to the default
value). For instance, this request to access phpinfo() produces this
stack trace in the apache error log:

[Tue Jul 9 07:48:33 2013] [error] PHP Warning: phpinfo() [<a
href='function.phpinfo'>function.phpinfo</a>]: It is not safe to rely on
the system's timezone settings. You are *required* to use the
date.timezone setting or the date_default_timezone_set() function. In
case you used any of those methods and you are still getting this
warning, you most likely misspelled the timezone identifier. We selected
'UTC' for 'UTC/0.0/no DST' instead in /home/y/share/htdocs/index.php on
line 2
[Tue Jul 9 07:48:33 2013] [error] PHP Stack trace:
[Tue Jul 9 07:48:33 2013] [error] PHP 1. {main}()
/home/y/share/htdocs/index.php:0
[Tue Jul 9 07:48:33 2013] [error] PHP 2. phpinfo()
/home/y/share/htdocs/index.php:2

Also, apache and php are compiled as 32 bit binaries to run on a 64 bit
OS, whereas the debugclient is compiled as a 64 bit binary, could this
cause any problems?

thanks for your help,
Vijay
Received on Tue Jul 09 2013 - 09:22:55 BST

This archive was generated by hypermail 2.2.0 : Mon Jun 25 2018 - 06:00:04 BST