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 1035 - VM thread dumps (e.g. initiated by Ctrl-\ or Ctrl+Break) should be captured to a log file.
Summary: VM thread dumps (e.g. initiated by Ctrl-\ or Ctrl+Break) should be captured t...
Status: RESOLVED DUPLICATE of bug 69277
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: All All
: P3 enhancement (vote)
Assignee: _ ttran
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 1999-01-15 00:59 UTC by Jesse Glick
Modified: 2008-12-22 09:49 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 1999-01-15 00:59:20 UTC 
Since all logging done by NetBeans--that is, to system/netbeans.log--is controlled by the NetBeans Java code, this file contains only things which that code decides to put there--mainly startup info
 and exception listings. However, VM thread dumps are sent to stderr by default (correct?) and this output is not redirected into the error log. Thus, a potentially critical piece of debugging informa
tion is potentially lost: on Unix, when invoking from a window-manager, the output might be sent to the XSession log if you are lucky; on Win32, the output can only be captured if the user has already
 set the NetBeans console window to keep a few hundred lines of scrollback buffer, which is not the default; and even if the output is still present in a scrolling buffer somewhere, it may be difficul
t to cut and paste it into a bug report (esp. on Win32)!

To reproduce: send NetBeans a Ctrl-Break in e.g. Win32 and note the lack of the output in netbeans.log, though it is sent to the console window.

[IAN] Since the redirection is done by Java code in netbeans and not using the OS`s redirection mechanisms, it is not possible to catch VM messages to the log

[IAN] Deferred for Gandalf

[jglick] see Workaround/Fix panes -->
Comment 1 Jan Zajicek 2001-01-23 09:30:59 UTC 
Automated change of version from Other to Dev.
Comment 2 Jesse Glick 2001-01-23 12:48:59 UTC 
BTW the (now-lost) Workaround pane suggested using something like this:

java org.netbeans.Main > ide.log 2>&1

(oversimplified).
Comment 3 Jan Chalupa 2001-05-05 20:32:37 UTC 
Target milestone -> 3.3
Comment 4 _ ttran 2001-07-10 23:13:07 UTC 
vstejskal is now the maintainer of the launcher
Comment 5 Jan Chalupa 2001-11-27 11:52:43 UTC 
Target milestone -> 3.3.1.
Comment 6 Jan Chalupa 2001-11-27 11:56:23 UTC 
Target milestone -> 3.3.1.
Comment 7 Jan Chalupa 2002-01-11 14:03:06 UTC 
Target milestone -> 3.4
Comment 8 Jan Chalupa 2002-01-11 14:07:03 UTC 
Target milestone -> 3.4
Comment 9 Jan Chalupa 2002-01-11 14:08:16 UTC 
Target milestone -> 3.4
Comment 10 Jan Chalupa 2002-01-11 14:11:13 UTC 
Target milestone -> 3.4
Comment 11 Jesse Glick 2002-01-21 14:34:22 UTC 
Note: this is easy to implement in the Unix launcher:

${java} .... 2>&1 | tee vm.log

or

${java} .... 2>vm.log

The runide.exe would need to also save it somehow, using whatever
Win32 call.
Comment 12 _ ttran 2002-01-30 10:04:07 UTC 
I am taking over this issue
Comment 13 Marek Grummich 2002-07-22 08:30:37 UTC 
Target milestone was changed from '3.4' to TBD.
Comment 14 Marek Grummich 2002-07-22 08:34:25 UTC 
Target milestone was changed from '3.4' to TBD.
Comment 15 _ rkubacki 2007-01-04 20:41:00 UTC 
There is another way how to achieve logging (to separate file) and some other
comments in issue 69277

tee - it is another process and outputs are not imediate
pure redirecting is bad as you might want to see it in console too 

*** This issue has been marked as a duplicate of 69277 ***