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.
I have used eclipse for quite some time and have shied away from prior versions of NB because eclipse was way better. Now NB seems to have caught up in the game, and i am glad about it. But, the java debugger aspect of NB still is ages behind eclipse and i can't understand why NB lags by so much in this feature. NB simple isin't exposing all the things one can do with the JDP at command line. Some of the things it currently supports are not intuitive and easy. I have too many complaints to list regarding the java debugger, and hence will summarise by saying that the NB debugger UI and the backend teams, should look (i.e. if they haven't already done so) at atleast eclipse to see how nice the eclipse debugger is. quick points, that i miss in NB for which there aren't even good workarounds and i use eclipse for these 1) multiple thread stack views, 2) evaluation of some expression at runtime (any expression relevant to the context of the debugger session and location)
Hello Kiran, let me comment on your P1 defect against NetBeans JPDA debugger. I know you suggested to take a general look at Eclipse functionality but could you please be specific what you see buggy here? I am sure you understand there is no point in submitting P1 bug and hoping we will rewrite whole debugger support in NetBeans from scratch within several weeks. Thus it would be more helpful to let us know about all concrete defects you spot in NetBeans 5.5. Now as for the two requirements you mentioned. You are right that we don't support multiple threads call stack views yet. However, your second item is available in NetBeans since version 5.0 already. Please invoke "Run|Evaluate Expression" from main menu while debugging session is stopped at breakpoint. So, I am adding an INCOMPLETE keyword to mark this issue as pending for your input. Please elaborate what this bug means otherwise we can't do much about your vague complaint. Did you encounter some deadlock, data loss or crash which is appropriate severity for P1 issue? Thanks for your feedback! Jiri Kovalsky NetBeans QE team
I should have said this is an enhancement. I didn't find any bugs. So i changed that. Sorry to take a harsh stance, but that is the reality as i see. Many developers shy aways from NB debugger GUI. I don't want to get into the story boarding business, instead am pointing to an existing IDE's debugger view and saying that all developers find it more useful. That should be a strong point to think about enhancing or rewriting if that is what is needed in NB JPDA. I am aware of the evaluateExpression. But what i am asking is something equivalent to execute a chunk of code at runtime. I can do this in eclipse. Refer to the "display" tab of the eclipse debugger, you can almost write a program on the fly while you are debugging. As i said it is an enhancement. The question is do we want to loose developer base to eclipse? Maybe that would make the NB debugger folks re-think what NB has today in JPDA support.
Improvements are in process. In NB 6.5 we have, for example, added a new Debugging view which joins threads and call stack views and adds additional functionality when multiple breakpoints are hit or a deadlock is detected. More improvements are planned into next NB 7.0.
The items you were talking about were improved in NB 6.7. We have Debugging window where individual threads can be easily stopped/resumed and where you see stack frames of stopped threads, including locks if "Show monitors" is on. You can also evaluate a code fragment in Evaluator window.
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.