steps to reproduce:
- start debug session
- open new project
while IDE is scanning debugger is unable to step or do anything
This can not be fixed, since we need the parser information to properly highlight where the debugger is stopped.
We could, in theory, just to show the regular line highlight when the parser information is not available. Bu we can never know when the parsing will be finished and this could cause that the more detailed highlighting will not be visible too often due to some random re-scanning of sources.
Martin, the project that I was debugging had been opened and fully parsed long ago, so all information should have been available. The project I opened was another project that had nothing in common with the project I was debugging. I understand that probably it should be fixed in code model, so that it provides information for already parsed projects and do not block if another project is being parsed, so maybe you could reassign it to parser if nothing could be done in debugger part?
it is really annoying: step over can be performed while scanning and it looks like debugger accepts it BUT it will really stop on the next line only after scanning is done!
Making this P2 for 7.2. Maybe this could be addressed even without 182653 being implemented. Please consult with Tomas Zezula. Thanks.
*** Bug 206846 has been marked as a duplicate of this bug. ***
Created attachment 115065 [details]
Jirka, your stack trace seems to be unrelated. There's nothing from debugger.
Comment on attachment 115065 [details]
You are right. It was added mistakenly by exception reporter.
The problem was also fixed on background_scan branch.
How it could be added by exception reporter, when there's nothing in "Exception Report" field in this issue?
Is there some severe bug in the exceptions reporter?
Fixed by changeset: 211053:5b10fd88134c
Integrated into 'main-golden', will be available in build *201201250600* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Log: #202573: Update the thread's operations lazily so that we do not have to wait for Java parser. After the operations are updated, refresh the current thread annotation, print more detailed message to Debugger Console and refresh Variables view to have the info about the current operation.