Scenario: Debug Morphic Layouting

[LinqLover]

• Roles: System outsider (nearly zero prior knowledge about the system), system expert (already knows precisely where to search)
• Goal: Understand the reason for an AssertionFailure signaled from #doLayoutAgain
• Example: Layouting of an etoys script morph (see EToys-ct.403 and "Etoys car example.1.cs")
• Problems: Narrowing down when the property #doLayoutAgain is added to the morph requires stepping into all details or performing a binary search by starting a new debugger whenever it was stepped too far.
• Possible solutions:
  • step into details later in the context of the original morph state
  • find all instructions in the trace that add the property #doLayoutAgain