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.
1. Create Quote sample project 2. Use Step into Project context menu to start debug session. 3. Make Local Variables View active 4. Use Step Over to navigate in debug session. Here is the issue: if you will use F8 not very slow ( as usual users do) Locals View will be repainted only on line 112. Meanwhile if you will be really slow it will be repainted in 3 seconds (which is really slow for local variables view and very visible to users)
Currently LV data is discarded if received after the user has pressed a step button. I can go ahead and display this data, but its already obsolete. To me, it doesn't seem particularly useful. I'll check with the dbxgui team and see what they do (others, too). If the consensus is that this data should be displayed I'll display it.
I was too optimistic when said it takes 3 seconds, in reality it takes from 6 to 8 seconds to update data after Step I think to wait 6-8 seconds (it takes so long when you do step) just to see *real* values in LV cannot be OK for any user (only if he/she wants to drink a cup of coffee (or hot tee) while debugging ;) )
What hardware are you using? I consistently see step working in 1/10 to 1/4 of a second. I almost never see it slower. If you're getting significantly slower results (and assuming its comparable hardware) then there must be some other reason.
It is not about step, it is about how long it will take to repaint LV after step
I'm still not clear on the exact behavior you're talking about. I'm seeing a performance problem on Windows which I don't see on Solaris and suspect its what you're talking about. But please help me verify this. On Windows (release551u1 bits), Julie stepped into Quote. She immediately had argc and argv showing in LV but nothing else. She stepped until 112 and the rest of the vars were displayed (after a 6-8 second display). Is this similar to what you're seeing? This behavior is definitely wrong. First off, you should see *all* vars in main as soon as you do the step-into-project (not just argc and argv). Second, it shouldn't take another 5-8 seconds to display the rest. Using my latest bits (grp-gdb551u1-wip) on Windows I get something more accurate but equally slow. I get an hourglass with the message "Please wait..." immediately in the LV. After 6-10 seconds it fills with the expected data. The data is now correct (I had to do a workaround for a gdb bug) but takes way too long to display. Turning on the gdb console window (-J-Dgdb.console.window=true) shows that some messages have been sent to gdb and not responded to. I plan on seeing if I can do a gdb command line test to see if this problem exists in gdb or in gdb-lite. If its a gdb problem, I'll add it to my list of gdb issues we need fixed, but it won't be fixed soon (I've joined the gdb community and plan on working on some of the issues affecting gdb-lite and submitting fixes). Anyway, the main thing I'd like to clarify is if the behavior Julie showed me is similar to what you're seeing or not. If you can compare results on both Solaris and Windows and comment on the differences that would also be useful. On Solaris, if I step into Quote I get all vars displayed in about a second (although they're all uninitialized). This is what *should* happen on Windows!
There were several problems. I think the last of them are fixed. Right now, I'm getting Quote to show in the Local Variables view in about 1 1/2 seconds on Windows (it was always faster on Solaris). Please reopen if you see a delay of more than 2-3 seconds for the 1st display
Verified in nightly build 20070915