Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <4.3.2.7.2.20020111042031.00b29120@san-francisco.beasys.com>
X-Sender: andyp AT san-francisco DOT beasys DOT com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 11 Jan 2002 04:22:12 -0800
To: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>, <cygwin AT cygwin DOT com>
From: Andy Piper <andyp AT bea DOT com>
Subject: Re: Ash spawning win32 programs (was Re: bash/cmd CTRL-C
  problem...)
In-Reply-To: <08a601c19a99$0aeb9690$0200a8c0@lifelesswks>
References: <4 DOT 3 DOT 2 DOT 7 DOT 2 DOT 20020111022918 DOT 00b63c68 AT san-francisco DOT beasys DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 11:11 PM 1/11/2002 +1100, Robert Collins wrote:
>Can I suggest you start a new thread when the topic changes, it helps
>prevent confusion - particulary if the original thread hangs around.

Sorry. I thought the two might be related.

> > Interactive bash shell starts:
> >          -> shell script using ash starts:
> >                  -> java program
> >
> > ^C-ing the script does not have any visible effect (i.e. the java
>program
> > is not killed). As noted previously this problem is resolved if you
>make
> > /bin/sh be bash rather than ash.
>
>Hmm. I'll look into this is you will :}.

Sure.

>I suspect that ash uses vfork rather than fork+exec to start it's child
>process's. That may result in no cygwin stub existing.
>
>here's what you need to do:
>
>write an ash script that prints out it's pid, and (if you can get it)
>the cygwin pid of the java program.
>
>Start the ash script in the background, and then use ps. See if the java
>program appears in ps. If it does - check via task manager or process
>explorer to see if the reported cygwin pid is the same as the actual
>java.exe pid.
>
>If it doesn't appear, then no cygwin stub exists, and quite some work
>may be needed to *efficiently* create such a virtual process. (it would
>be quite trivial via the daemon :})
>
>If it does appear, and the shown cygwin pid is the same as the java.exe
>pid, then no stub exists, but the bulk of the code to have a 'virtual'
>process is there, but signals aren't working correctly.
>
>If it does appear, and the shown cygwin pid is different than the actual
>java.exe pid, then there is a stub, and things should be working
>correctly - I'll take a direct look at this point.

Ok thanks. I'll see what I can do.

andy


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/