public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin" <cygwin@cygwin.com>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: Re: Question about executable startup failure
Date: Thu, 14 Nov 2019 17:15:00 -0000	[thread overview]
Message-ID: <MN2PR09MB39654358CBEF23CD3FBE987AA5710@MN2PR09MB3965.namprd09.prod.outlook.com> (raw)

> > During startup program exited with code 0xc0000139.

> so Windows handles termination.

IMO if it did, the exit code wouldn't have been 127 but something with decimal equivalent of 0x139 (or the likes).

> P.S. I didn't get to know what exactly the entry point was missing that the 
> binary required (obviously from the newer Cygwin ABI).

Running under strace gets a Windows error popup "thebadexecutable.exe - Entry Point Not Found", that says inside:

---
The procedure entry point uname_x could not be located in the dynamic link library
C:\Cygwin64\home\user\thebadexecutable.exe
---

where thebadexecutable.exe in the above, is the executable being attempted to run.

In case of running it from the shell, nothing like that appears.

--
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:[~2019-11-14 16:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-14 17:15 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-11-14  8:55 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-11-14 16:37 ` Brian Inglis

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=MN2PR09MB39654358CBEF23CD3FBE987AA5710@MN2PR09MB3965.namprd09.prod.outlook.com \
    --to=cygwin@cygwin.com \
    --cc=lavr@ncbi.nlm.nih.gov \
    /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).