When the variable being tracked by UpdatingDisplayValue becomes no longer available, UpdatingDisplayValue should fire off an event.
As a note, this should cover functions returning both normally and abnormally (exception, longjump, task dying).
UpdatingDisplayValue now notifies its observers when the variable passes out of scope due to a function return ChangeLog: frysk.rt: 2007-06-22 Adam Jocksch <ajocksch@redhat.com> * DisplayValue.java (refresh): Disabled stack backtraces when DebugInfo.print throws exceptions. * DisplayValueObserver.java (updateUnavailableOutOfScope): Added. * TestUpdatingDisplayValue.java (testUpdateUnavailableFuncReturn): Added code, enabled test. (DisplayObserver): Refactored to reflect changes to the interface. * UpdatingDisplayValue.java (refresh): If the value retrieved is null, notify the observers. (notifyObserversUnavailableOutOfScope): New method.
UpdatingDisplayValue now correctly signals when a variable has fallen out of scope due to a call to (sig)longjmp. frysk-core/frysk/pkglibdir: 2007-06-25 Adam Jocksch <ajocksch@redhat.com> * funit-rt-varlongjmp.c: New file. frysk-core/frysk/rt: 2007-06-25 Adam Jocksch <ajocksch@redhat.com> * TestUpdatingDisplayValue.java (createDaemon): Now takes the name of the program to start. (testUpdateTaskStopped): Refactored for above change. (testUpdateValueChanged): Ditto. (testUpdateUnavailableFuncReturn): Ditto. (testUpdateUnavailableLongjump): Implemented, addresses part of bz#4639.