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 82308 - "Build Project" can print over 100 identical warning messages in output window
Summary: "Build Project" can print over 100 identical warning messages in output window
Status: VERIFIED FIXED
Alias: None
Product: cnd
Classification: Unclassified
Component: Project (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Michal Skvor
URL:
Keywords: USABILITY
: 80389 82579 82639 83533 84976 85499 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-08-09 18:24 UTC by Nikolay Molchanov
Modified: 2008-02-04 16:02 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nikolay Molchanov 2006-08-09 18:24:17 UTC
I noticed this problem when I tried to eliminate warning messages,
that appear during building sample project Quote. If I modify file
system.cc and press "Build Project" button, there are over 100 (!)  
identical "blue" messages in output window:

system.cc:52: warning: comparison between signed and unsigned integer expressions
system.cc:52: warning: comparison between signed and unsigned integer expressions
system.cc:52: warning: comparison between signed and unsigned integer expressions
system.cc:52: warning: comparison between signed and unsigned integer expressions
...


From command line it works just fine.
=====================================
bash-3.1$ cd c:/tmp/nikm/Quote1
bash-3.1$ g++    -c -g -Wall -o build/Debug/GNU-Windows/system.o system.cc
system.cc: In member function `Module* System::GetModule(int)':
system.cc:52: warning: comparison between signed and unsigned integer expression
s
system.cc:54: warning: control reaches end of non-void function
bash-3.1$

I use build 060809 (Aug 09 2006) on Windows XP with latest Cygwin compilers.
I set high priority P2, because it is very visible problem.
Comment 1 alexandrov 2006-08-14 13:27:19 UTC
Just want to add:
In case of uncompilabe code you will not see the reason of build fail(after all
warning messages).
Comment 2 _ gordonp 2006-08-14 17:32:33 UTC
*** Issue 82579 has been marked as a duplicate of this issue. ***
Comment 3 soldatov 2006-08-15 07:43:00 UTC
*** Issue 80389 has been marked as a duplicate of this issue. ***
Comment 4 alexandrov 2006-08-15 08:07:58 UTC
*** Issue 82639 has been marked as a duplicate of this issue. ***
Comment 5 _ gordonp 2006-08-15 22:36:53 UTC
This problem results from a change to o.n.m.cnd.execution.OutputWindowWriter
(version 1.1.2.7). In this change a zero length file named ".fail" is created
in the directory of a file causing an error. However, the file is never
removed so the next time an error is found in the same directory, the creation
of the ".fail" file fails and throws an uncaught FSException.

Checkin comments are vague as to what this fix helps: "Added hack to obtain
fail from execution". As a temporary fix I'm commenting out the
FileObject.createData calls. This may break the intended functionality, but
the current problems breaks very simple builds and seems much more serious.

I'll reassign to Michal Skvor so he can fix his change.
Comment 6 _ gordonp 2006-08-28 17:20:55 UTC
*** Issue 83533 has been marked as a duplicate of this issue. ***
Comment 7 soldatov 2006-09-15 11:20:29 UTC
*** Issue 84976 has been marked as a duplicate of this issue. ***
Comment 8 _ gordonp 2006-09-22 19:33:26 UTC
Since this is fixed in cnd and is being tracked as unfixed, I'm closing it
as fixed. Michal can open a related IZ if he needs to track the ".fail" file
feature Mobility used.
Comment 9 _ gordonp 2006-09-22 19:34:02 UTC
*** Issue 85499 has been marked as a duplicate of this issue. ***
Comment 10 Alexander Ioffe 2008-02-04 16:02:19 UTC
Verified in build 20080204