Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Starter.exe

Actually in Win priority range for the threads has 31 level.
Starter exists because of GenerateConsoleCtrlEvent causes Ctrl event (Ctrl-C
for example) to come to all process in the target group. So using this
function in spawner causes that javaw process itself gets this event.
starter is a leader of new group and protects javaw.
I don't see any problem to transmit priority setting or any other command
through starter to launched process.
I'll check if in cygwin Ctrl-C doesn't work. So far I haven't gotten any
complains about that. Thanks for the information.

Alex Chapiro

----- Original Message -----
From: "Chris Songer" <songer@xxxxxxxxxxxxx>
To: <cdt-dev@xxxxxxxxxxx>
Sent: Monday, February 03, 2003 11:04 PM
Subject: [cdt-dev] Starter.exe


> Hi!
>
> The real challenge with all of this setpri stuff is the starter.exe for
NT.
> Everything else is just easy. Does anyone have any background on why
> starter.exe is there? Is it because you need to have something to be the
> head of a process group for NT's GenerateConsoleCtrlEvent to work? That's
> my suspicion.
>
> If so, it does not appear to interoperate well with cygwin and I think it
> will only work for Ctrl events on non-cygwin apps. So not only is it
> screwing me over for setting priority ( going to have to create an event
to
> send it since the pid held in spawner.dll is for starter and not what
> starter started ) but it's ALSO not working for cygwin apps since cygwin
> has to be the process group leader before it will turn a CTRL_C_EVENT into
> a SIGINT.
>
> Thanks!
> -Chris
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev
>



Back to the top