[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] Spawner command line lenght limitations?
|
Good point. Then I guess we should be fixing it up so that it doesn't run
into these restrictions. As Mikhail mentioned, he has risen a bug on this.
Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead, Tools PMC member
http://cdtdoug.blogspot.com
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of Lott, Jeremiah
Sent: Tuesday, April 25, 2006 2:11 PM
To: CDT General developers list.
Subject: RE: [cdt-dev] Spawner command line lenght limitations?
----Original Message----
From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
Sent: Tuesday, April 25, 2006 2:01 PM
To: CDT General developers list.
Subject: RE: [cdt-dev] Spawner command line lenght limitations?
> I am wondering if we are overusing the Spawner framework. My
> understanding is that it was really only meant for debug that had
> specific requirements on process management.
>
> I have removed its use for invoking the ctags indexer and now use
> java.lang.Process directly. No problems so far...
>
> Doug Schaefer, QNX Software Systems
> Eclipse CDT Project Lead, Tools PMC member
> http://cdtdoug.blogspot.com
>
It also does some other magic right? I remember seeing some posts.
Something about setting up the process group correctly under windows so
that Process.destory() works better? Otherwise when you cancel a build
on windows it kills only the top-level process, and any subprocesses
continue to run. Also, I think it sets up a pseudoterminal on linux,
which is useful when launching user programs, since some of them need
that. The one for the pseudoterminal is here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=27663
Jeremiah Lott
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
