Community
Participate
Working Groups
Build ID: M20070212-1330 Steps To Reproduce: 1. create a fifo in an existing project directory using something similar to mkfifo("./myfifo", 0777); 2. select Project, Clean 3. Eclipse will hang in the build, before the compiler is invoked. More information: Have reproduced this many times. Work around is to be sure the remove any fifo files from my project directory before invoking the build.
I am facing the same problem. I need a FIFO in the project as its a part of my project. its 2012 August. this bug is not fixed yet?
I don't see the hang if I create "myfifo" in a project by I do see it if I rename it so a source file, myfifo.cpp. Is the file a source or header file?
I am not using CDT. but using Eclipse for PHP (aka PDT). This is how I reproduce it. 1. Create a PHP project. 2. Open shell and create a fifo in the project directory using mkfifo fifo 3. Now go to that eclipse project and refresh the project tree. This will hang. Unlike CDT, PDT does not compile anything as PHP is a scripting language. But what it does is create an index of classes/functions/methods so that all of them can be found in the drop down. Some sort of intellisense. In PHP "build" refers to this. If there is any syntax error build can trace it
(In reply to comment #3) > I am not using CDT. but using Eclipse for PHP (aka PDT). This is how I > reproduce it. Can you create a bug against PDT instead? The platform doesn't have a fix for this AFAIK (bug 213207) so the issue will have to be worked around in both PDT and CDT. (In reply to comment #3) > Unlike CDT, PDT does not compile anything as PHP is a > scripting language. But what it does is create an index of > classes/functions/methods so that all of them can be found in the drop down. > Some sort of intellisense. In PHP "build" refers to this. If there is any > syntax error build can trace it CDT does something similar, it also has an indexer that creates an index. The hang also happens on CDT when the indexer tries to read the FIFO.
*** This bug has been marked as a duplicate of bug 505968 ***