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 199434 - With no warning whatsoever the G++ / Make will stop acting properly with the netbeans compiler, despite 'good' code being fed into it.
Summary: With no warning whatsoever the G++ / Make will stop acting properly with the ...
Status: RESOLVED FIXED
Alias: None
Product: cnd
Classification: Unclassified
Component: execution (show other bugs)
Version: 7.0
Hardware: PC Windows 7 x64
: P2 normal (vote)
Assignee: Andrew Krasny
URL: http://www.youtube.com/watch?v=dOSABk...
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-15 14:25 UTC by sarevok9
Modified: 2011-06-15 17:47 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description sarevok9 2011-06-15 14:25:33 UTC 
The youtube video linked above is it happening to me in realtime.   You'll notice that after the crash, I simply restart netbeans and recompile.   This sort of thing happens to me quite a bit.  

I have turned off profiling tools, and have ensured that I have gdb / G++ / make /gcc and they are all working.

I have no idea how to recreate this bug.   It seems to happen to me about 1/10-15 times I try to compile code.   It's typically non-bugged code, that should / will run after a quick restart of netbeans.

Further system info:
Computer model number: Samsung Rf-711-02
Windows 7 Ultimate (legally obtained)
4gb of ram
Intel i7 -2630QM Quad Core (2.0ghz)


Something else I've noticed that I feel is worth mentioning is that when this happens, I try to kill the thread (hitting stop, even hitting the x in the bottom right) and nothing will kill the task.   

Hopefully this is something that has been identified in a more clear manner.

I am making this bug report based on the advice of soldatov in this thread:
http://forums.netbeans.org/viewtopic.php?t=39889


Thanks kindly.
Comment 1 Andrew Krasny 2011-06-15 17:47:01 UTC 
This is a problem with a deadlock in internal terminal. 
The fix is pushed in release701 branch (201002:3fd2f34b7f0c).
Will appear in dev builds rather soon.

as a workaround - you may try to use output window instead of internal terminal ('run' tab in project's properties)