The following bug has been RESOLVED.
======================================================================
http://bugs.xdebug.org/bug_view_page.php?bug_id=0000327
======================================================================
Reporter: MikeD
Handler: derick
======================================================================
Project: Xdebug
Bug ID: 327
Category: Usage problems
Reproducibility: always
Severity: major
Priority: normal
Status: resolved
Operating System:
PHP Version: 5.1.2
Xdebug Version: 2.0.0
Resolution: not a bug
======================================================================
Date Submitted: 2007-10-26 16:13 CEST
Last Modified: 2007-10-27 18:10 CEST
======================================================================
Summary: xdebug.var_display_max_* values are ignored in remote usage
Description:
running xdebug for remote debugging, however it seems that the
xdebug.var_display_max_children, xdebug.var_display_max_data,
xdebug.var_display_max_depth settings in php.ini are ignored and internal
default values are used. Note that these internal values used are
different from the normal defaults
xdebug.var_display_max_data:
normal default: 512
php.ini setting: 2048
queried value: 1024
xdebug.var_display_max_children
normal default: 128
php.ini setting: 2048
returned value: 32
xdebug.var_display_max_depth
normal default: 3
php.ini setting: 20
returned value: 1
workaround:
when debugging session launches send these DBGp commands to reset the
configurations to the desired values:
feature_set -i 1 -n max_children -v <value>
feature_set -i 2 -n max_data -v <value>
feature_set -i 3 -n max_depth -v <value>
======================================================================
----------------------------------------------------------------------
derick - 2007-10-27 18:10 CEST
----------------------------------------------------------------------
This is not a bug, those three settings are not supposed to work on remote
debugging. The defaults need to be different as it is a bad idea to have a
depth != 1 for remote debugging, while it also cumbersome to deal with
var_dump() displays if the depth = 1 there. I updated the documentation
for those 3 settings to make this a bit clearer.
Bug History
Date Modified Username Field Change
======================================================================
2007-10-26 16:13MikeD New Bug
2007-10-26 16:13MikeD Bug Monitored: MikeD
2007-10-27 18:10derick Bugnote Added: 0000766
2007-10-27 18:10derick Assigned To => derick
2007-10-27 18:10derick Resolution open => not a bug
2007-10-27 18:10derick Status new => resolved
======================================================================
Received on Sat Oct 27 2007 - 18:10:33 BST
This archive was generated by hypermail 2.2.0 : Sun Jun 24 2018 - 04:00:03 BST