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.
This issue was originally marked as duplicate of issue 166406, that is already resolved. This issue is still valid, so this seems to be another issue, but it might be related. Build: NetBeans IDE Dev (Build 200907070200) VM: Java HotSpot(TM) Client VM, 10.0-b23, Java(TM) SE Runtime Environment, 1.6.0_07-b06 OS: Windows XP, 5.1, x86 User Comments: GUEST: Right click on c++ project and click jn project properties chrikoch: trying to open properties of a project by rigth-cliking the project and the selecting properties. GUEST: Right click on c++ project and click on project properties GUEST: pressed run! boom! error! damerian: Tryiing to run a project which builts succesfully charlweed: Properties context menu for c++ project. mromashova: Just opened project in the IDE Stacktrace: java.lang.NullPointerException at java.lang.ProcessBuilder.start(ProcessBuilder.java:441) at org.netbeans.modules.nativeexecution.support.HostInfoImpl.getLocalHostInfo(HostInfoImpl.java:128) at org.netbeans.modules.nativeexecution.support.HostInfoImpl.getHostInfo(HostInfoImpl.java:100) at org.netbeans.modules.nativeexecution.support.HostInfoFetcher.getInfo(HostInfoFetcher.java:82) at org.netbeans.modules.nativeexecution.api.util.HostInfoUtils.getHostInfo(HostInfoUtils.java:301) at org.netbeans.modules.dlight.util.Util.copyResource(Util.java:87)
Created attachment 85104 [details] stacktrace
This issue already has 10 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=154081
This issue already has 21 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=154081
This is already fixed in current trunk: http://hg.netbeans.org/main-golden/rev/7bd0e166cc33 Probably should be included into next 6.7 patch.
This issue already has 51 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=154081
This issue already has 52 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=154081
The issue is resolved in 6.8. Keep it open for possible 6.7.2 patch.
*** Issue 170492 has been marked as a duplicate of this issue. ***
*** Issue 170701 has been marked as a duplicate of this issue. ***
This issue already has 150 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=154081
This issue already has 151 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=154081
This issue already has 154 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=154081
This makes it impossible to do C or C++, so must be in the next 7 patch. Going to the 8 nightlies prevents me from using some of my plugins.
Is it really impossible for you to install cygwin on your Windows machine? cygwin/mingw was listed in requirements for C/C++ pack and that is why it was never tested on systems without one of these tools. I don't know about plans for 7.x patches... Will try to figure-out. If there are some plans for this I will do my best to solve this issue. =Andrew
I have both Cygwin and MinGw installed and got this!
Why should anyone install Cygwin or/and Mingw, if he use remote compilation? I, for example, use remote compilation only.
Well... I have prepared a jar file that will likely help you. It is not well tested yet though.. Once I'll get a confirmation that it works, I'll ask to push this fix to the NB6.7 UpdateCenter. Meanwhile, for those who are interested in the fix: could I ask you to try to copy the jar (attached) and try your remote development? You should replace original jar located in {NB installation directory}/dlight1/modules/ Thanks in advance, =Andrew P.S. In any case - if you have an opportunity to switch to 6.8 - please do so.
Created attachment 88446 [details] A hack to overcome the problem
Created attachment 88447 [details] A hack to overcome the problem
Sorry for a wrong attachment - one should use *.jar file, not *.nbm!
Thanks for patch, it works.
Good to know, thanks! (Somehow I missed that sharkman confirmed that patch is OK. Thanks, sharkman!) So... will try to put it on UC...
*** Issue 173459 has been marked as a duplicate of this issue. ***
Is not reproducible in NB 6.8 and 6.9. All reported exceptions regard only NB 6.7 and 6.7.1