From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: cannot execute binary file
Date: Wed, 02 Nov 2011 11:01:00 -0000 [thread overview]
Message-ID: <4EB122D6.3070003@cs.umass.edu> (raw)
In-Reply-To: <4EB10244.3000901@gmail.com>
On 11/2/2011 3:41 AM, Marco Atzeri wrote:
> On 11/2/2011 9:10 AM, Edvardsen KÃ¥re wrote:
>>
>> Are there any debug options or logs to check when you get "cannot
>> execute binary file"?
>>
>> Cheers,
>> KÃ¥re
>
> - if is it a permission problem you need to check the ACL permissions
> see getfacl or ACL permission from windows explorer
>
> - if you are missing dll's, you can check with:
> cygcheck ./nome_of_your_file
> ldd ./nome_of_your_file
An additional thought is to use strace to see the exact
sequence of OS calls and results. You would strace bash
and type your command at bash, then examine the strace
output ...
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-02 11:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 10:24 Edvardsen Kåre
[not found] ` <4EAFE5F0.7090404@cs.umass.edu>
2011-11-01 13:00 ` Edvardsen Kåre
2011-11-02 8:11 ` Edvardsen Kåre
2011-11-02 8:42 ` Marco Atzeri
2011-11-02 11:01 ` Eliot Moss [this message]
2011-11-01 14:32 ` Edvardsen Kåre
-- strict thread matches above, loose matches on Subject: below --
2013-12-16 22:55 Gerry Reno
2013-12-17 0:27 ` Max Polk
2013-12-17 0:32 ` Gerry Reno
2013-12-17 2:39 ` Larry Hall (Cygwin)
2013-12-17 2:58 ` Gerry Reno
2013-12-17 9:35 ` Andrey Repin
2013-12-17 12:44 ` Tim Prince
2013-12-17 16:27 ` Gerry Reno
2013-12-17 18:59 ` Gerry Reno
2012-09-21 4:23 RobF
2012-09-21 7:54 ` P.Long
2012-09-21 8:27 ` Csaba Raduly
2012-09-21 13:06 ` RobF
2011-11-02 10:04 Edvardsen Kåre
2006-09-07 18:08 Cannot " Arun Biyani
2006-09-07 18:19 ` Dave Korn
2006-09-07 18:27 ` Christopher Faylor
2006-09-07 18:50 ` Arun Biyani
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=4EB122D6.3070003@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).