Red Hat Bugzilla – Bug 119371
Poor handling of out-of-scope variables in debugger ui
Last modified: 2014-08-11 01:46:18 EDT
Description of problem:
When watching variables, any that go out of scope are dealt with very
Version-release number of selected component (if applicable):
Steps to Reproduce:
1. Debug a simple testcase which has a function with a variable in it.
Break in this function.
2. Add the expression for the local variable (right click->Add Expression"
3. Step out of function to caller. Notice that there is no indication
that the variable is now out of scope UNLESS you click on the variable.
4. Try to modify the out-of-scope variable.
In #3, no indication that variable is out of scope. The UI simply does
not notice (yes, MI can deal with this situation)
In #4, you get the nice error message: "Setting the variable value
failed. Reason: Target request failed: mi_cmd_var_assign: Could not
assign expressin to varible object". How quaint.
In #3 it should NOT show a value for the variable -- it should show an
error message (like "out of scope" or something).
It should simply not allow the user to even attempt to modify a
variable out of scope.
Closing old bug; either fixed or should be reported upstream.