Message-ID: <4EB3C378.6060308@cs.umass.edu>
Date: Fri, 04 Nov 2011 05:50:32 -0500
From: Eliot Moss <moss@cs.umass.edu>
Reply-To: moss@cs.umass.edu
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: =?UTF-8?B?RWR2YXJkc2VuIEvDpXJl?= <kare.edvardsen@uit.no>
CC: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Problem with execution of binary file
References: <1320322806.5480.161.camel@kare-desktop> <4EB30E21.3090707@cs.umass.edu> <1320396611.5480.196.camel@kare-desktop>
In-Reply-To: <1320396611.5480.196.camel@kare-desktop>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 11/4/2011 3:50 AM, Edvardsen Kåre wrote:
>
>> On 11/3/2011 4:56 PM, Eliot Moss wrote:
>>          Ok, so here's one thing about bash: to get it to
>>          run an *executable* (as opposed to a *script*),
>>          you need to say "bash -c FLEXPART_GFORTRAN".
>>          You might try strace on that. In addition to the
>>          objdump suggestion.
>>
>> I have a moment to expand on this a little. The
>> 80-byte read we saw was bash looking at the
>> beginning of what it that was supposed to be a
>> script (not a binary) and seeing if it really
>> appeared to be a script. I did not look like a
>> script, so bash gave up. (It checks whether the
>> first line is all printable characters or white
>> space.)
>>
>> Best -- Eliot Moss
>>
>
> Hmm, wonder why bash would interpret it as a script. Anyway, I will get
> back to you later with output from strace and objdump.

Because you did not specify -c ... EM

--
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