Bug 560248 - [functional debug expr] Support access to 'this' and 'super' in functional expressions
Summary: [functional debug expr] Support access to 'this' and 'super' in functional ex...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.15   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks: 560247
  Show dependency tree
 
Reported: 2020-02-17 20:32 EST by Jesper Moller CLA
Modified: 2024-01-29 20:33 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jesper Moller CLA 2020-02-17 20:32:38 EST 
Currently, access to the surrounding 'this'-object, including qualified references to outer classes' 'this'-references, does not work in functional expressions inside debugger expressions.

This can be fixed by binding access to 'this' to an explicit enclosing this, at it seems that just making the SnippetClass non-static will cause a VerifyError, probably because of all the special cases handled in CodeSnippetCompiler and friends.
Comment 1 Eclipse Genie CLA 2022-02-07 12:25:53 EST 
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 2 Eclipse Genie CLA 2024-01-29 20:33:10 EST 
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.