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.
When hitting the first breakpoint, if the Call Stack pane was selected, nothing appear there. (see attached image). There is an easy workaround though, you just have to select for example the "Local Variables" pane and then back "Call Stack" and it work. So it's the initial repaint when hitting a breakpoint that is not OK.
Created attachment 52138 [details] Empty Call Stack
Product Version: NetBeans IDE 6.0 Beta 2 (Build 200710212201) Java: 1.5.0_07; Java HotSpot(TM) Client VM 1.5.0_07-87 System: Mac OS X version 10.4.10 running on i386; MacRoman; en_US (nb) Userdir: /Users/cedric/.netbeans/6.0beta2
This really looks like a repaint problem, according to the scroll bar. Will try to reproduce...
Can you please check whether the content is painted when you move the scroll bar?
no, actually I cannot move the scrollbar. moreover, when I click on local variables and back to call stack the scrollbar disappear (my stack trace is short).
Note that this problem really only occur on first breakpoint when starting to debug. On all further breakpoint (or single stepping) the update is properly done immediately.
Seems to be Mac-specific. I can not reproduce this on Linux. Will try on some Mac machine later...
Maybe a repaint problem of TreeTableView? Or it can be a swing issue. Incomplete repaints often happen to me when having IDE on other virtual screens and I guess that it's a swing bug. Moving to openide/tree table view for evaluation...
I'm seeing what may be the same issue with 6.5.1. The Call Stack window is showing no threads at all .. usually when my application is running I can see all of the running threads and a call stack when I'm at a breakpoint.. but in 6.5.1 the view is often blank.
Sorry that last comment applies to the Debugging View - not the call stack. I will file a new issue.
This seems to work correctly in NB 6.7. Can you please verify there? Debugger views were rewritten to use Outline view, therefore it likely fixed this inconsistency.