Bug 576376 - Cannot set breakpoint from nested class
Summary: Cannot set breakpoint from nested class
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.22   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-01 03:23 EDT by Ed Willink CLA
Modified: 2023-09-22 02:28 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 Ed Willink CLA 2021-10-01 03:23:00 EDT
In the debugger I have a field whose type is

org.eclipse.emf.ecore.xmi.impl.EcoreResourceFactoryImpl$1

I Open Actual Type. The code is

  @Override
  public Resource createResource(URI uri)
  {
    XMLResource result = 
      new XMIResourceImpl(uri)
      {
        @Override
        protected boolean useIDs()
        {
          return eObjectToIDMap != null || idToEObjectMap != null;
        }
      };
    result.setEncoding("UTF-8");
...

I double click the left vertical bar for the result.setEncoding line following the nested class. No breakpoint is set.

It seems that the 'editor' opened as and titled EcoreResourceFactoryImpl$1 has inadequate knowledge of all the surrounding lines that it displays. However the editor does have some knowledge since the override decorations and navigate to superclass actions work.

Ideally WYSIWYG but failing that as a minimum a popup should offer to open the surrounding EcoreResourceFactoryImpl class file where breakpoints could work. And failing that, rather than the 'working' lines of the nested class having a confusing darket grey background, the 'context' surrounding lines should have a reddish error / hatched / greyed out appearance.
Comment 1 Eclipse Genie CLA 2023-09-22 00:27:57 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 2 Ed Willink CLA 2023-09-22 02:28:09 EDT
Cannot be stalebug till triaged by a relevant committer.