Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 311504

Summary:

Display debug doesn't work in anonymous class containing special generics

Product:

[Eclipse Project] JDT

Reporter:

Anthony Ogier <netangel+eclipse>

Component:

Debug

Assignee:

JDT-Debug-Inbox <jdt-debug-inbox>

Status:

RESOLVED WORKSFORME

QA Contact:

Severity:

normal

Priority:

CC:

sarika.sinha

Version:

3.5.2

Target Milestone:

4.12 M3

Hardware:

OS:

Linux

Whiteboard:

stalebug

Attachments:

Description	Flags
BugTest.java : the class which contains the bug	none

Description Anthony Ogier

2010-05-04 05:58:53 EDT

Build Identifier: 20100218-1602

In the code submitted with this bug report, the Display view cannot evaluate the value of a variable and shows "(No explicit return value)" instead of the value of the variable.

Reproducible: Always

Steps to Reproduce:
1. Create the class "BugTest" submitted with this bug report
2. Add a break point near line 19, on "System.out.println(valueObject);"
3. Run the main in debug mode
4. When the debugger stops, open the Display view
5. Write valueObject in the Display view
6. When hovering the text valueObject in the view, I can see an inspect popup describing the fields of my valueObject, BUT, when I select the text and press Ctrl+D or Ctrl+I to print the value of valueObject or inspect it, I've got "(No explicit return value)" instead.

Comment 1 Anthony Ogier

2010-05-04 06:01:22 EDT

Created attachment 166926 [details]
BugTest.java : the class which contains the bug

Comment 2 Eclipse Genie

2019-05-09 18:50:22 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 Sarika Sinha

2019-05-10 00:47:21 EDT

Looks like it got resolved . Can't reproduce in
Eclipse SDK

Version: 2019-06 (4.12)
Build id: I20190508-1800