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 151401 - Debugging Sources window is corrupt, cannot use breakpoints
Summary: Debugging Sources window is corrupt, cannot use breakpoints
Status: CLOSED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on: 90398
Blocks:
  Show dependency tree
 
Reported: 2008-10-26 22:45 UTC by _ gtzabari
Modified: 2010-04-29 09:45 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
My userdir (199.70 KB, application/x-compressed)
2008-10-26 22:46 UTC, _ gtzabari 		Details
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 _ gtzabari 2008-10-26 22:45:54 UTC 
dev build 200810221401

I debugged a project for several hours today. All of a sudden my breakpoints no longer work. The debugger work reads:

Not able to submit breakpoint LineBreakpoint AdministratorsTest.java : 99, reason: Breakpoint belongs to disabled source
root 'C:\Users\Gili\Documents\method\trunk\adcaster\Server\test'. See Window/Debugging/Sources.

I go into Window/Debugging/Sources only to find that the "Use for Debugging" column is empty. Normally this has a
checkbox that indicates whether a source is enabled or not but it is getting rendered as an empty cell.

Please see my attached userdir. I've deleted /var because it isn't necessarily to reproduce the bug (deleting it doesn't
make the problem go away).
Comment 1 _ gtzabari 2008-10-26 22:46:51 UTC 
Created attachment 72665 [details]
My userdir
Comment 2 Martin Entlicher 2008-11-18 11:32:01 UTC 
Sources window is planned to be improved in 7.0.
Comment 3 Daniel Prusa 2009-05-05 10:40:26 UTC 
Not reproducible now. There were many fixes/improvements regarding sources view, this problem should be solved.
Comment 4 Quality Engineering 2010-04-29 09:45:09 UTC 
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.