This is sources Bugzilla
Bugzilla Version 2.17.5
Bugzilla Bug 5362
  frysk.scopes is too closely wired to dwfl Last modified: 2008-03-25 17:42
     Query page      Enter new bug
Bug#: 5362   Hardware:   Reporter: Andrew Cagney <cagney@redhat.com>
Host: Target: Build:
Product:     Add CC:
Component:   Version:   CC:
Remove selected CCs
Status: ASSIGNED   Priority:  
Resolution:   Severity:  
Assigned To: Unassigned <frysk-bugzilla@sourceware.org>   Target Milestone:  
Summary:
Keywords:

Attachment Description Type Created Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 5362 depends on: Show dependency tree
Show dependency graph
Bug 5362 blocks:

Additional Comments:


Leave as ASSIGNED 
Mark bug as waiting for feedback
Mark bug as suspended
Resolve bug, changing resolution to
Resolve bug, mark it as duplicate of bug #
Reassign bug to
Reassign bug to owner of selected component

View Bug Activity   |   Format For Printing


Description:   Last confirmed: 0000-00-00 00:00 Opened: 2007-11-19 16:28
Contrast the implementation with frysk.value which is disconnected from the Dwfl
(via frysk.debuginfo.TypeAttribute aka TypeFactory).

------- Additional Comment #1 From Sami Wagiaalla 2007-11-27 20:46 -------
For this the LocationExpression code needs to be changed to take an a mediating
object instead of variable die.

This issue will also pop up for the Type code particularly returning the value
of a static data memeber.

public Value getValue(DebugInfoFrame frame) {
	List ops = variableDie.getFormData(frame.getAdjustedAddress());
	ISA isa = frame.getTask().getISA();
	LocationExpression locationExpression = new LocationExpression(frame,
variableDie, ops);
	PieceLocation pieceLocation
	    = new PieceLocation(locationExpression.decode(this.getType(isa)
							  .getSize()));
	Value value = new Value(this.getType(isa), pieceLocation);
	return value;
    }

     Query page      Enter new bug
Actions: New | Query | bug # | Reports | Requests   New Account | Log In