[Cdt-launch-inbox] [Bug 102043] Console Output Does Not Appear When Laun

[bugzilla-daemon@xxxxxxxxxxx]

https://bugs.eclipse.org/bugs/show_bug.cgi?id=102043





------- Additional Comments From j_apter@xxxxxxxxxxx  2005-08-30 07:30 -------
(In reply to comment #14)
> (In reply to comment #13)
> > Yes, we agree it's a problem. However, given all the other things we need to do,
> > this hasn't risen in priority enough for someone to look at.
> > 
> > Certainly a patch that fixes the problem would go a long way to ensuring this
> > gets fixed.
> 
> I'm afraid that you underestimate the bad impact of this bug. CDT simply is not
> usable on Windows. New users will throw it away as unusable crap - they will not
> even see their "Hello World!" and old users must use old versions unless they
> find this bug and use the Sleep(1) workaround.
> 
> If someone is new to Win API as I was, then please include windows.h and
> winbase.h to get Sleep working.

I've got to agree with this, though, I can somewhat understand Doug's standpoint
from an engineering perspective.  For what it's worth, I spent about an hour
looking into this problem with the debugger and didn't really get anywhere. 
These kinds of threading issues are no fun (maybe this is part of the reason why
no one wants to fix it, hehe).

Also note that the Sleep(1) workaround doesn't seem to work for me 100% of the
time (results will vary on different machines due to the nature of the bug).  A
more reliable workaround is to remove/rename the spawner.dll file (located in
org.eclipse.cdt.core.win32_3.0.0\os\win32\x86).  This will force CDT to use
Runtime.exec() instead which, for some reason, does not seem to have the same
problem (note that this will cause the loss of some functionality, see comment #9).

I propose that spawner.dll be renamed or removed from the CDT distribution
altogether until a fix could be found.  This workaround requires no code
modifications.  I do realize that this may be somewhat drastic as not all
applications suffer from this issue (e.g. GUI applications), so they may not
wish to lose the functionality mentioned in comment #9, but maybe this will be
motivation to fix the underlying problem.  :)

Also, I'm not entirely convinced that this is a Windows only bug, could someone
test this on Linux?

Anyways, just my $.02...



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.