X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 	tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <BLU0-SMTP73EE1BECC810EFEE13E1FEBE8E0@phx.gbl>
MIME-Version: 1.0
In-Reply-To: <1ef5a52f0912090205v2b8bb67cgcca943b8e64061f1@mail.gmail.com>
References: <BLU0-SMTP101BC8B0315A89E9D551E94BE8F0 AT phx DOT gbl> 	 <1ef5a52f0912090205v2b8bb67cgcca943b8e64061f1 AT mail DOT gmail DOT com>
Date: Wed, 9 Dec 2009 11:01:47 -0500
Subject: Re: 1.5.25-15: Problem running rpmbuild from a bash script
From: Matt Rice <citrusmoose AT hotmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Wed, Dec 9, 2009 at 5:05 AM, Csaba Raduly <rcsaba AT gmail DOT com> wrote:
> On Tue, Dec 8, 2009 at 8:16 PM, Matt Rice =A0wrote:
>> I'm having problems running rpmbuild from a bash script. =A0The problem
>> occurs when I run the script outside an interactive bash prompt.
> (snip)
>> =A0According to the bash manual, the 128 status code means it
>> terminated on a signal of 0.
> According to the Perl documentation (perldoc perlvar, $CHILD_ERROR),
> the 128 status code from a child process (in fact any status code
> which contains the 0x80 bit) means there was a core dump.

That may very well be.  But I can't really determine anything because
I get no error messages.

Also, I got desperate, so I uninstalled cygwin, changed some
permissions on the root cygwin directory, then reinstalled.  Now I'm
able to run the bash command in a windows prompt.  However, I'm
ashamed to say this wasn't my real problem.  Currently, I have a
Bamboo windows service running (under the SYSTEM account).  This
process is what calls bash.exe.  I thought since the windows prompt
was acting the same way, fixing one would fix both.  I was obviously
wrong.

I know that there are issues with sshd running on 2003 under SYSTEM.
Could this be the same issue?  Is there anything I can do to get more
information from the failed command?

- Matt

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple