Bug 4575 - DisplayValue tracks variables leaving scope
Summary: DisplayValue tracks variables leaving scope
Status: RESOLVED FIXED
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Adam Jocksch
URL:
Keywords:
Depends on:
Blocks: 4547
  Show dependency tree / graph
 
Reported: 2007-05-31 17:36 UTC by Adam Jocksch
Modified: 2007-06-01 20:01 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Jocksch 2007-05-31 17:36:26 UTC 
When the variable tracked by a DisplayValue falls out of scope, the DisplayValue
should reflect it.
Comment 1 Adam Jocksch 2007-06-01 20:01:25 UTC 
This now works, and is confirmed by TestDisplayValue.testVarOutOfScope.

frysk-core/frysk/rt:
2007-06-01  Adam Jocksch  <ajocksch@redhat.com>

	* DisplayValue.java (DisplayValue): Now takes the name of the variable
	as a string, the task from which it should be fetched, and the FrameIdentifier
	indicating the scope it is in.
	* TestDisplayValue.java (testVarOutOfScope): Enabled, confirms bz#4575
	as fixed

frysk-core/frysk/pkglibdir:
2007-06-01  Adam Jocksch  <ajocksch@redhat.com>

	* funit-rt-varchange.c: Made the variables static volatile and
	added a variable to function bar.