public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Problem with execution of binary file
Date: Thu, 03 Nov 2011 12:53:00 -0000	[thread overview]
Message-ID: <20111103125258.GA15704@calimero.vinschen.de> (raw)
In-Reply-To: <1320322806.5480.161.camel@kare-desktop>

On Nov  3 12:20, Edvardsen KÃ¥re wrote:
> I keep getting the "cannot execute binary file" and don't understand
> why. I have compiled same software on two different machines, but only
> one of the binaries work (it works on both machines). The successful
> machine is a HP laptop with W7 Pro, the other unsuccessful is a HP
> desktop in a AD network domain with W7 Enterpr and cygwin is installed
> with lokal admin rights only, so I keep getting the "Your group is
> currently mkpasswd..." message.

What about running

  $ mkpasswd -l -d > /etc/passwd 
  $ mkgroup -l -d > /etc/group 

so you don't get this message?

> I don't know if this may affect the
> result, but should not, as I can run the other successful binary.
> 
> I was guided to run "strace" along with the call to the erroneous binary
> and the output is pasted below. The problem binary is called
> "FLEXPART_GFORTRAN" Can anyone see what's wrong in the strace log?

No.  What the strace shows is that bash does not even try to fork
and then exec FLEXPART_GFORTRAN.  Rather, it just opens the file,
reads the first few bytes and then prints the error message:

>  4514  125618 [main] bash 536 open: open (./FLEXPART_GFORTRAN, 0x0)
>  [...]
>    25  126365 [main] bash 536 open: 3 = open (./FLEXPART_GFORTRAN, 0x0)
>   209  126574 [main] bash 536 isatty: 0 = isatty (3)
>  [...]
>    25  126623 [main] bash 536 lseek64: 0 = lseek (3, 0, 1)
>  [...]
>    24  126710 [main] bash 536 readv: 80 = readv (3, 0x28CA34, 1), errno
> 0
>   458  127168 [main] bash 536 open: open
> (/usr/share/locale/locale.alias, 0x0)
>   [...etc...]

For some reason which isn't visible in the strace, bash doesn't even
close the file anymore.

What does `file FLEXPART_GFORTRAN.exe' print?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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

  reply	other threads:[~2011-11-03 12:53 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 [this message]
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
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=20111103125258.GA15704@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --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).