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.

Bug 20556 - Enhance debugger console to display tracing information
Summary: Enhance debugger console to display tracing information
Status: REOPENED
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 5.x
Hardware: PC Windows 3.1/NT
: P3 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
: 32960 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-02-14 17:32 UTC by Peter Kalab
Modified: 2011-09-20 15:40 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Kalab 2002-02-14 17:32:12 UTC
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
Comment 1 Marek Grummich 2002-07-22 09:15:50 UTC
Target milestone was changed from '3.4' to TBD.
Comment 2 Marek Grummich 2002-07-22 09:19:39 UTC
Target milestone was changed from '3.4' to TBD.
Comment 3 _ lcincura 2005-05-12 14:56:32 UTC
Debugger console is implemented, all that has to be done is to add more tracing
messages to it :-)
Comment 4 Martin Entlicher 2005-05-13 10:50:14 UTC
*** Issue 32960 has been marked as a duplicate of this issue. ***
Comment 5 ceklock 2011-09-20 15:40:39 UTC
Reopening... checking old issues...