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.
CND build from 060227, JDK 1.5.0u6, Linux fedora core 4 The output from build action in IDE looks like this - heapTracker.c: In function âworkerâ: heapTracker.c:200: error: âgc_countâ undeclared (first use in this function) heapTracker.c:200: error: (Each undeclared identifier is reported only once heapTracker.c:200: error: for each function it appears in.) heapTracker.c: In function âcbVMInitâ: heapTracker.c:339: error: âerrâ undeclared (first use in this function) make: *** [heapTracker.o] Error 1 It looks OK when I do the build on command line - heapTracker.c: In function ‘worker’: heapTracker.c:200: error: ‘gc_count’ undeclared (first use in this function) heapTracker.c:200: error: (Each undeclared identifier is reported only once heapTracker.c:200: error: for each function it appears in.) heapTracker.c: In function ‘cbVMInit’: heapTracker.c:339: error: ‘err’ undeclared (first use in this function) make: *** [heapTracker.o] Error 1 It means quotes are mangled somewhere.
Jan Lahoda suggests: ...It reads data from an InputStream and puts them into a Writer, but it does not correctly translate bytes into chars. I would try to rewrite it as follows (in principle): /** This is all output, not just stderr */ private Reader err; private Writer output; public ExecutionProcessThread(InputStream err, Writer output) { this.err = new InputStreamReader(err); this.output = output; } It seems right to me. I'm sure this will not break anything (that is not already broken :-)), but I need to find a platform where it fails to really confirm this also fixes it.
I have not been able to find a platform where it fails so I will commit the suggested fix as is. It doesn't break anything, but without a failing test case, it is hard to say with 100% certainty that it does fix the problem. Gordon reported seeing a similar problem with NB5.0 (no CND module), so perhaps the problem is really somewhere else. Please reopen if you see this again.
Verified in build 31102007