This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 100201 - Return values history node disappear after step into+step out in the expression
Summary: Return values history node disappear after step into+step out in the expression
Status: NEW
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Martin Entlicher
URL:
Keywords:
: 132886 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-04-06 11:07 UTC by ehucka
Modified: 2010-07-30 10:58 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ehucka 2007-04-06 11:07:05 UTC
NetBeans IDE Dev (Build 200704051800)
1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105
Linux version 2.6.16-1.2122_FC5 running on i386

Example:

System.out.println((msgMemory.format (new Object[] {
                                      new Long (total),
                                      new Long (free),
                                      new Integer (taken)})));

Steps:
1. Invoke Step Over Expression in this expression to display Return values
history node in Local Variables view with one return value - first of 'Long()'
constructors.
2. Invoke Step into on the second constructor
3. Invoke Step Out from the constructor code
4. The return value will be there
5. Invoke Step Over Expression

Result: 'Return values history' node will disappear and will not be shown after
any of another steps in the expression.
Comment 1 Martin Entlicher 2007-04-06 12:52:46 UTC
This is a known limitation so far. I've already though about fixing this, but
it's not really easy to determine that we're returning to the same evaluation of
the expression.
But this is still on our radar and hopefully be fixed for 6.0.
Comment 2 ehucka 2007-04-06 13:34:22 UTC
I think there should be started new evaluation with new return values node when
it is not possible to determine if it is the same evaluation as before step into.
Comment 3 Roman Ondruska 2007-10-03 15:41:50 UTC
I was able to reproduce no return values are being created after reenter to the expression. After this is fixed, the
issue can be moved to RFE.
Comment 4 Daniel Prusa 2009-10-12 15:47:18 UTC
*** Issue 132886 has been marked as a duplicate of this issue. ***