Bug 384355 - Variables are not automatically displayed in debugger
Summary: Variables are not automatically displayed in debugger
Status: UNCONFIRMED
Alias: None
Product: Epsilon
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Dimitris Kolovos CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-05 08:12 EDT by Jason Hampson CLA
Modified: 2012-07-05 08:21 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Hampson CLA 2012-07-05 08:12:47 EDT
Build Identifier: Build id: 20100218-1602

When you run the debugger, the in scope variables are not automatically shown. The user has to select the individual stack frame for the variables to appear. This could be selected automatically when the script runs, or the variables could be shown when the thread is selected.  

When a user steps in the debugger, the thread is re-selected and the variable list clears, so you have to re-select the stack frame.

In the Java debugger, when a variable is selected the toString() value is displayed below the variable list. The Epsilon debugger does not do this, and the value may be too large to fix into the value column  

 

Reproducible: Always
Comment 1 Jason Hampson CLA 2012-07-05 08:21:31 EDT
Also, the debugger does not currently support watched expressions, as is possible from the Java debugger