Re: NetBeans debugger: suspend and see current stack trace how?



Lew wrote:

Because my answer was about NetBeans. It was ludicrous to take an
answer about NetBeans and say that it must apply to something else.
My answer was about NetBeans. I was talking about NetBeans (6.5).

Ah ha! NB 6.5 is still in beta. I assumed 6.1, which is the current release version.


So, again, here's the information I was trying to give you - NetBeans
has the feature that when you suspend a program in the debugger, there
is a window with all the extant threads visible in the debugger view.

Not by default, although once you open the window in the debugger, it will show the Threads window again next time it is started, at least on the same project.

If you (double-)click on one of the threads in that window, actually
on one of the expanded items within that thread, it will take you to
the corresponding line of source in the editor window, if available.

Not in 6.1. The work around I posted previously does a decent job. I'm looking forward to 6.5's new features.



Note that the debugger view in NetBeans is not a separate
"perspective" but merely the view you have when you invoke the
debugger. Invoking the debugger automatically brings up certain
windows not otherwise usually on the screen.

Only Local Variables, Call Stack, and Breakpoints are open by default on the current stable release of NetBeans. The other 7 odd debugger windows have to be opened manually. Although as I mentioned it seems to remember the windows you had open last time you invoked the debugger and will open those for you again.


Overall, a little snarkiness by both of you. Lew, you should have mentioned you were using a beta build, because it *is* different than the stable version. Nelson, you should have actually looked for a debugger windows named "Threads" rather than posting the quip you did. That's how I found it, by looking.


.



Relevant Pages

  • Re: NetBeans debugger: suspend and see current stack trace how?
    ... the corresponding source in the source window. ... Eclipse is the IDE with separate coding and debugging ... Because my answer was about NetBeans. ... is a window with all the extant threads visible in the debugger view. ...
    (comp.lang.java.programmer)
  • Re: NetBeans debugger: suspend and see current stack trace how?
    ... the corresponding source in the source window. ... Because my answer was about NetBeans. ... has the feature that when you suspend a program in the debugger, ... is a window with all the extant threads visible in the debugger view. ...
    (comp.lang.java.programmer)
  • Re: netbeans doesnt create lib directory under dist
    ... The fundamental issue has to do with how to tell NetBeans to include ... Lew is correct that that is derived from ... brings up the project properties window. ... there is a Libraries selection which brings up a tabbed window. ...
    (comp.lang.java.programmer)
  • Re: AppleWin Debugger & AppleWin Ports
    ... I found the single-screen debugger constraining at first ... do what I needed within the window. ... the command line/docs are a little too obtuse for it ... debugger and set a breakpoint at $300, switch back to the emulator and CALL ...
    (comp.emulators.apple2)
  • Debugging
    ... On my WinXP Professional box at home, I can't get the debugger to start from ... I get the same error using NetBeans 3.5.1, ... The command the IDE is trying to execute - shown in the output window - is ...
    (comp.lang.java.softwaretools)