Multihreaded debugging planned for Netbeans 6.5


News: Multihreaded debugging planned for Netbeans 6.5

  1. Netbeans developers are planning lots of fixes and improvements for the next version (6.5). But one of them is particularly interesting for those who already tried to debug a multithread system: multithreaded debugging support. The matter is that, in "normal" debuggers, you can debug only a single thread, meanwhile lots of things happen behind you, in other threads. But next Netbeans version will bring us this shiny tool. Some screenshots show that this new feature will be very intuitive and easy to use. Everything is visual and include some nice features, like a deadlock detector. Netbeans developers had to change threading model, to be able to implement this new feature. According to Netbeans wiki, some points are summarized below:
  2. Default breakpoint only suspends breakpoint thread.
  3. Step only resumes current thread when invoked and suspends current thread when completed.
  4. Evaluation is done resuming the current thread (other threads unsuspended by default breakpoint or step). No deadlock caused by debugger might happen as far as no thread is explicitly suspended by the user (via suspend action or some breakpoint).
  5. 'Step interrupted by a breakpoint' issue does not exist with default breakpoint. (Except the stepping thread itself encounters a breakpoint.)
  6. You can see more details at Netbeans Wiki or Bistro Java

Threaded Messages (7)

  • I wonder how this thing compares with Eclipse thread debugging that had multi-session debugging from the beginning and deadlock detection for several years.
  • Netbeans[ Go to top ]

    Sorry to rant here. But it simply makes me sad. Netbeans always has been my favorite among the ides because it does so many things right. Yet I dont use it. The problem I see is that Netbeans always is the 95% better than the rest 5% vital percent missing IDE. It is simply amazing how they push out new features, but then it simply falls flat on its face in the vital five percent. Examples: Javascript support really well working but it falls flat on its face once it comes down to handling prototype functions in the code insight or by adding basic refactoring support. Profiler: Tried it with 5.5 awesome UI, could not use it due to Bugs (they are probably fixed by now). Integration of Subversion, excellent among the best, but then no server view, which is vital if you work with Subversion, again the missing 5% which makes me use alternatives. Project support, excellent with ant and maven. Yet maven lacks artefact search other plugins provide. Add to that that incremental compilation still is missing which is one of the big features of eclipse (especially if you use it with tools like javarebel) The list of those things is way longer those are just the examples which I remember. It always is like that. I want to switch to Netbeans and then relatively quickly I hit the wall in the non visual parts of the IDE and I always think in the next version those small 5% will be fixed... Dont get me wrong as I said, Netbeans does so many things right, but always those five percent are worse than the rest, and usually those are vital. If Netbeans once can get those 5% in, then it probably is the best IDE there is.
  • Re: Netbeans[ Go to top ]

    It's one of the reasons I finally moved to Eclipse. Netbeans seems to have focus on all the features, but QA seems to be a lesser concern. I was constantly running into issues with something working fine at first glance, but falling apart once you try to do something more serious with it (I won't mention how many bugs I run into in the XML editor alone, just for DTD/Schema functionality). In the end I moved to Eclipse...sure, maybe they don't go as crazy on the features (although there are plenty of them and some, such as incremental compilation are better), but in 99.9% of the cases, when it's there it just works. From a stability point of view, Eclipse has an edge here. As for Matisse, NB's biggest advantage for a long time, I stopped needing it once I discovered MigLayout, the essential tool in any Swing developer's toolbox. :-)
  • Not to highjack the thread here, but I was recently involved in a rapid prototype GUI project, and I had the choice between SWT and Swing. I had dabbled with both in the past and really loved SWT/Eclipse Visual Editor for initial GUI layout. Now I discover it no longer works with Eclipse Ganymede... So I Switched to NetBeans 6.1. My experience was so-so, and I found that I don't like Swing as much as SWT. Maybe it was the whole forms/binding idea. Do any of you guys know of an equivalent tool for SWT thats *NOT* really old? Thanks.
  • Re: Speaking of SWT/Swing[ Go to top ]

    JIDE:, haven't found anything that's even near this in terms of accelerating Swing development.
  • Using VE with Ganymede is possible, you just have to use a patched version. The process is described here: The patched VE can be fetched from:
  • Spelling[ Go to top ]

    Hmm: "Multihreaded debugging ..." Was that suppose to be "MultiTHREADED debugging" or "MultiHEADED debugging"? It kind of could go either way.