Bug 303981 - Debugger expressions show "no explicit return value" with double-nested inner class
Summary: Debugger expressions show "no explicit return value" with double-nested inner...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows 7
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-25 18:06 EST by Cory Burkhardt CLA
Modified: 2022-08-21 17:23 EDT (History)
0 users

See Also:


Attachments
Class that demonstrates the bug (435 bytes, text/java)
2010-02-25 18:08 EST, Cory Burkhardt CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Cory Burkhardt CLA 2010-02-25 18:06:59 EST
Build Identifier: 20090920-1017

If the debugger breaks inside of a double-nested inner class, with the inner-most class accessing a member variable of the outer class, all expressions in the Expressions view display a "No explicit return value" message and give null for the value.  Even putting in a literal expression such as 3 or "a string" gives this result.

See the attachment for an example.

Reproducible: Always

Steps to Reproduce:
1. Create a project and add the attached .java file.
2. Set a breakpoint on line 15 (marked with a comment).
3. Launch the debugger and hit the breakpoint.
4. Open the "Expressions" view and add any expression.
Comment 1 Cory Burkhardt CLA 2010-02-25 18:08:09 EST
Created attachment 160259 [details]
Class that demonstrates the bug
Comment 2 Eclipse Genie CLA 2020-07-20 08:57:32 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 3 Eclipse Genie CLA 2022-08-21 17:23:01 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.