Community
Participate
Working Groups
'Change Value' on a variable in Expressions view causes nothing (in case of ZendDebugger). 1. Create following PHP code. <?php $obj = array(1,2,array("a","b","c")); var_dump($obj); ?> 2. Debug as PHP Web Page with Zend + Break at First Line 3. Select "$obj" and add watch.(rightclick->watch, show view->Expressions) 4. Do StepOver. $obj appears in Expressions view. 5. Change value $obj[0] ((int) 1) for example. The value won't be changed. 6. Change value $obj[2][0] ((string:1) a) for example. The value won't be changed and value pane shows wrong(entered) value. In case of Xdebug, 'Change Value' causes error message-box. It says >Setting the value failed. > >Reason: > program under debug rejected value change
For xdebug, it would seem that xdebug refused the request to change the value from PDT. So this might be a feature of xdebug rather than a bug in PDT.
DBGpVariable in Expressions View doesn't have fullname value even if it is a php variable.
For xdebug, I have disabled the ability to change a value in an expression. It would only make sense if you were watching just a variable. The facility to change variable contents is available from the variables pane. This however doesn't apply to the zend debugger.
Addressed in XDebug
Same goes for the Zend debugger ,but we need to add a relevant message OR disable this action.
Reproducible in PDT 2.0.0 as well using ZendDebugger Tested on Wix XP Eclipse SDK Version: 3.4.1 Build id: M20080911-1700 debugger - org.zend.php.debug_feature-I20081127 pdt - N20081201 dltk-core-sdk-I-I200811251145-200811251145-incubation [Kalin Yanev kalin.a@zend.com]
Can't re-create. I go to Variables View, change value of $obj[0], press F8 - and I see new value in the Debug Output View.
The value changed after F6 pressed. There is no changed after pressing OK on "Change Value" window. Still relevant. Reopening, moving to 2.2.0M1
Created attachment 182349 [details] patch This patch can fix it in "Variables" view. But in "Expressions" view, I find it also can't refresh the value when I change it in JDT. So I think it's a bug of platform.
