This is the mail archive of the
mailing list for the Cygwin project.
Re: Problem with execution of binary file
- From: Edvardsen KÃre <kare dot edvardsen at uit dot no>
- To: "moss at cs dot umass dot edu" <moss at cs dot umass dot edu>
- Cc: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Fri, 4 Nov 2011 08:50:41 +0000
- Subject: Re: Problem with execution of binary file
- References: <1320322806.5480.161.camel@kare-desktop> <4EB30E21.email@example.com>
> 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
> 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.