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.
Summary: | Avoid spam in the log if the -XX:+HeapDumpOnOutOfMemoryError option is not supported by the JVM | ||
---|---|---|---|
Product: | platform | Reporter: | Victor Vasilyev <vvg> |
Component: | Launchers&CLI | Assignee: | Antonin Nebuzelsky <anebuzelsky> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | jtulach |
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Proposed patch |
Description
Victor Vasilyev
2010-07-01 15:29:07 UTC
Created attachment 100547 [details]
Proposed patch
To fix this issue the attached patch could be applied to the script
o.n.bootstrap/launcher/unix/nbexec
It will redirect spam to the /dev/null.
"What does &>" do different than ">"? (In reply to comment #2) > "What does &>" do different than ">"? It also redirects stderr where we have spam from JVM. OK, if you think the "&>" is correct and will work on all platforms, go on and integrate your change. I don't think &> is correct here. This format of redirection is mentioned only in the documentation of bash, while docs of sh do not mention it at all. 2>&1 is what redirects stderr to where stdout is redirected. So, to me the current statement in nbexec is formally correct ( > /dev/null 2>&1 ). Also I could not reproduce the reported problem with OpenJDK 6 on my ubuntu box. I don't see any "spam" in the output. |