> > During startup program exited with code 0xc139.
> 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 re
On 2019-11-13 23:48, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote:
> Here's a situation: I have a binary that was built (from a C source code)
> with Cygwin 3.0.7 but "accidentally" used with much older Cygwin 2.11.2.
>
> The binary won't actually launch. Instead, it most uneventfully (s
Hi all,
Here's a situation: I have a binary that was built (from a C source code) with
Cygwin 3.0.7 but "accidentally" used with much older Cygwin 2.11.2.
The binary won't actually launch. Instead, it most uneventfully (silently, no
crash - no drama) exits with an exit code of 127, meaning "co
3 matches
Mail list logo
