This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: 1.5.25-15: Problem running rpmbuild from a bash script

On Wed, Dec 9, 2009 at 5:05 AM, Csaba Raduly <> wrote:
> On Tue, Dec 8, 2009 at 8:16 PM, Matt Rice ?wrote:
>> I'm having problems running rpmbuild from a bash script. ?The problem
>> occurs when I run the script outside an interactive bash prompt.
> (snip)
>> ?According 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

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:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]