Question about executable startup failure
Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
cygwin@cygwin.com
Thu Nov 14 17:15:00 GMT 2019
> > 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
More information about the Cygwin
mailing list