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 255431 - Step into doesn't work
Summary: Step into doesn't work
Status: NEW
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 8.0.1
Hardware: PC Mac OS X
: P3 normal (vote)
Assignee: Martin Entlicher
Depends on:
Reported: 2015-09-20 12:15 UTC by codenameone
Modified: 2015-09-21 08:36 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description codenameone 2015-09-20 12:15:42 UTC
This problem has been going on for quite a while and makes debugging almost useless. It happens on all my projects and I have no idea why. 

In debugging, step over works fine.
If I press step into all the debugger controls become disabled and nothing else happens! The only workaround to get out of that situation (without stopping the debugger) is the special per-thread play button in the debugger console.
I can demonstrate to step into I need to guess the destination method (which is hard with polymorphism) and place a breakpoint there.

The video of the issue is a bit big so I hosted it here: 
notice I press step into and all the controls become disabled. I then place a breakpoint in the method to show that the code wasn't reached yet and that nothing happened really.

This happened with Java 6, 7 and 8 and doesn't seem to be VM specific. I'm guessing something broke in my install. I can probably wipe out NB and cleanly install but setting it up properly (after the last time I did it) was a disaster...
Comment 1 Martin Entlicher 2015-09-21 08:06:04 UTC
What are the sources that you're debugging?
There's no paintComponent() method in java.awt.Component
And java.awt.Graphics does not have getClipX() method.

When I'm trying to step into methods on java.awt.Graphics, it works fine for me.

Can you please check a latest 8.1 dev build if step into works there?
The symptoms looks similar to issue #255126 which was fixed recently.
Comment 2 codenameone 2015-09-21 08:36:30 UTC
That's Codename One:

It happens with any set of sources regardless of whether I step into a library or within my code.
As I said, this has been going on for quite some time and is unique to my environment. I'll try 8.1.