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.
One feature missing from the Netbeans debugger is the ability to capture certain information (e.g. current stack trace, local variables) in a format that can be saved to a file for later analysis, or side-by-side comparison with another debug session. I'm thinking specifically of my current situation, where I am trying to figure out why a particular feature works through one code path, but not another - being able to see stack traces of how the code got to a specific place would be useful, as would a trace of code lines stepped through. If a stack trace could be dumped to the output window, I could then cut and paste that to a file and save it for analysis. To get a better idea of what I mean, take a look at the JSwat debugger (http://bluemarsh.com/java/jswat), which has a console window in addition to the GUI. From the console, I can type "where" to get the current stack trace. The console output can be cut and pasted to another window, or JSwat allows simultaneous logging of console output to a file (this will also show where breakpoints were hit and how code was single stepped. Thanks, Peter
Target milestone was changed from '3.4' to TBD.
Debugger console is implemented, all that has to be done is to add more tracing messages to it :-)
*** Issue 32960 has been marked as a duplicate of this issue. ***
Reopening... checking old issues...