From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11409 invoked by alias); 4 Nov 2011 10:50:57 -0000 Received: (qmail 11398 invoked by uid 22791); 4 Nov 2011 10:50:56 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,TW_BJ X-Spam-Check-By: sourceware.org Received: from csmail.cs.umass.edu (HELO csmail.cs.umass.edu) (128.119.240.177) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 04 Nov 2011 10:50:42 +0000 Received: from [192.168.0.6] (c-71-192-247-69.hsd1.ma.comcast.net [71.192.247.69]) by csmail.cs.umass.edu (Postfix) with ESMTPSA id 3553DB80001CDFB276; Fri, 4 Nov 2011 06:50:41 -0400 (EDT) Message-ID: <4EB3C378.6060308@cs.umass.edu> Date: Fri, 04 Nov 2011 10:50:00 -0000 From: Eliot Moss 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?= CC: "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 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2011-11/txt/msg00059.txt.bz2 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