Description of problem:
When watching variables, any that go out of scope are dealt with very
poorly.

Version-release number of selected component (if applicable):
20040329 nightly

How reproducible:
Every time

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.

  
Actual results:
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.

Expected results:
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.

Additional info: