From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: Problem with execution of binary file
Date: Fri, 04 Nov 2011 01:54:00 -0000 [thread overview]
Message-ID: <4EB345C3.2030408@cs.umass.edu> (raw)
In-Reply-To: <4EB30E21.3090707@cs.umass.edu>
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
--
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
next prev parent reply other threads:[~2011-11-04 1:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 12:21 Edvardsen Kåre
2011-11-03 12:53 ` Corinna Vinschen
2011-11-03 13:22 ` Eliot Moss
2011-11-03 14:11 ` Edvardsen Kåre
2011-11-03 19:54 ` Mark Geisert
2011-11-03 21:57 ` Eliot Moss
2011-11-04 1:54 ` Eliot Moss [this message]
2011-11-04 8:51 ` Edvardsen Kåre
2011-11-04 10:50 ` Eliot Moss
2011-11-04 12:34 ` Edvardsen Kåre
2011-11-04 17:56 ` Mark Geisert
2011-11-04 18:00 ` Eliot Moss
2011-11-04 18:21 ` Mark Geisert
2011-11-05 9:52 ` David Sastre
[not found] <1320325271.5480.163.camel@kare-desktop>
2011-11-03 13:19 ` Edvardsen Kåre
2011-11-07 9:55 Edvardsen Kåre
2011-11-07 19:26 ` Mark Geisert
2011-11-08 10:02 ` Mark Geisert
2011-11-08 10:08 ` Mark Geisert
2011-11-08 11:22 Edvardsen Kåre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EB345C3.2030408@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).