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 52601 - debugging of core java classes
Summary: debugging of core java classes
Status: CLOSED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 4.x
Hardware: PC Windows ME/2000
: P2 blocker (vote)
Assignee: issues@debugger
URL:
Keywords: USABILITY
Depends on:
Blocks: 90398
  Show dependency tree
 
Reported: 2004-12-17 12:04 UTC by drscott
Modified: 2010-05-10 09:04 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

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 drscott 2004-12-17 12:04:32 UTC 
Hi!

There is a problem with debugging core java
classes (e.g. java.util.Vector).

If you set an breakpoint in, say Vector.get(...),
the debugger stops at that position. Now, it is
not possible to use the various step commands
(step in, step out, next...).
Comment 1 Jan Jancura 2004-12-17 13:27:24 UTC 
Do you have JDK sources available for debugging? See Main
menu-Windows-Debugging-Source tab, and check JDK sources there.
Comment 2 drscott 2004-12-17 13:48:09 UTC 
well, ok, that solved part of the problem: a reference to the sources
is in that list, but it was not 'enabled' (use for debugging). After i
enabled it, debugging worked.

But: if the sources are not enabled for debugging, the debugger
shouldn't stop at breakpoints in that scope.

Anyway, i think JDK sources should be enabled by default. What do you
think?

Bug #51901 may be the same problem...
Comment 3 Jan Jancura 2005-04-13 09:28:37 UTC 
No chance to fix it in 4.1.
Comment 4 Martin Entlicher 2005-06-07 12:04:59 UTC 
IMHO either the JDK sources should be enabled as soon as there is a breakpoint
hit in JDK sources, or at least, it should be suggested to the user to enable
the JDK sources.
Comment 5 Martin Entlicher 2005-12-13 10:01:47 UTC 
This is a source of user confusion and needs to be fixed. Scheduling for 5.1.
Comment 6 Jiri Prox 2007-09-17 20:16:21 UTC 
Obsolete milestone, please reevaluate
Comment 7 drscott 2007-09-18 08:31:42 UTC 
using nb60beta1:

behaviour slightly changed: debugger ignores active breakpoints in 'disabled' sources. This is still not optimal. If the
user is able to set a breakpoint, he expect it to work.
Comment 8 Martin Entlicher 2009-11-16 08:56:49 UTC 
This is fully fixed in NB 6.8. Breakpoints and stepping in JDK sources are enabled by default.
Comment 9 Marian Mirilovic 2010-05-10 09:04:50 UTC 
verified closed