Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>,
	<http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Thu, 19 Aug 1999 18:26:47 -0400
To: Suhaib Siddiqi <ssiddiqi AT ipass DOT net>
Cc: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: FW: Description of the new 'ntsec' feature
Message-ID: <19990819182647.A12555@cygnus.com>
Reply-To: cygwin AT sourceware DOT cygnus DOT com
Mail-Followup-To: Suhaib Siddiqi <ssiddiqi AT ipass DOT net>,
	cygwin AT sourceware DOT cygnus DOT com
References: <19990819123559 DOT B11216 AT cygnus DOT com> <NDBBLHPPKKBKPBLLMFJBCEOHCBAA DOT ssiddiqi AT ipass DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.6i
In-Reply-To: <NDBBLHPPKKBKPBLLMFJBCEOHCBAA.ssiddiqi@ipass.net>; from Suhaib Siddiqi on Thu, Aug 19, 1999 at 12:34:52PM -0400

On Thu, Aug 19, 1999 at 12:34:52PM -0400, Suhaib Siddiqi wrote:
>> >snapshots).  Mostly I see this message (proc_info_signal 1000)
>> >when MAKE finishes compilation job.
>>
>> You're going to have to provide an actual error message, Suhaib.
>> The string proc_info_signal does not show up anywhere in cygwin.
>>
>> There is a proc_info structure and a sig_send function.  The sig_send
>> function could emit errors in some situations.  This is probably what
>> you're seeing and is probably what we need to track down.
>
>
>Sorry Chris, my poor memory of remembering the exact langauge.  I did post a
>cut and pawst later in responbse to Corinna's post.
>If you have not received it, please let me know, I will report it.

Yes, I saw it.  Sorry.  I've been in rush mode lately and have made the
mistake of not reading the complete thread before responding more than
once.

If you could do this:

strace -f -ostrace.out bash

and then try to duplicate that error, it would be immensely useful.
The strace.out file may be enough to pinpoint what's going wrong.

-chris

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com