public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Soegtrop, Michael" <michael.soegtrop@intel.com>
To: Wouter van Doorn <wouter@vandoorn.tv>,
	"cygwin@cygwin.com"	<cygwin@cygwin.com>
Subject: RE: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
Date: Tue, 27 Jun 2017 08:14:00 -0000	[thread overview]
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A175B276ED1@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <CANZ2p_cgEkm9KSb-3YLbo=gvk8O+NB0dAsFn5TSw-zuY0tP5SQ@mail.gmail.com>

Dear Wouter,

> One day on, and it's all reverted. Everything failing again in exactly the same way
> as before. It was too good to be true...

You might want to disassemble the good and bad binaries and compare the disassemblies. This should reveal what is going on. You can send me the binaries via private mail (as zip encrypted). Please note that the PATH has not only an influence at build time, but also at run time.

> I'll have to give up on cygwin, still appreciate the attempts at helping me.

You shouldn't. Of cause there is bogus SW which just isn't worth it, but Cygwin definitely doesn't fall into this category. 

One more advice: if computers behave erratically and don't have ECC memory, it is worthwhile to run a memory test (use memtest86, burn a boot CD and run it for 1 hour - don't trust in BIOS memory tests). I see broken memory about once or twice a year.

Best regards,

Michael
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

--
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:[~2017-06-27  8:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21 21:10 Wouter van Doorn
2017-06-21 21:49 ` René Berber
2017-06-22 13:13   ` Wouter van Doorn
2017-06-22 13:57     ` cyg Simple
2017-06-22 15:57       ` Wouter van Doorn
2017-06-26 14:16         ` cyg Simple
2017-06-26 18:51           ` Wouter van Doorn
2017-06-22 14:09     ` René Berber
2017-06-22 16:01       ` Wouter van Doorn
2017-06-22 16:19         ` René Berber
2017-06-22 19:11           ` Wouter van Doorn
2017-06-22 17:46         ` Soegtrop, Michael
2017-06-23  0:50         ` Andrey Repin
2017-06-23 19:30           ` Wouter van Doorn
2017-06-22 22:33     ` Thomas Wolff
2017-06-25  6:16       ` Wouter van Doorn
2017-06-25  6:23         ` René Berber
2017-06-25  6:32           ` Wouter van Doorn
2017-06-25 16:04             ` Brian Inglis
2017-06-25  8:33 ` Achim Gratz
2017-06-25  8:50   ` Houder
2017-06-26 19:01 ` Wouter van Doorn
2017-06-27  7:26   ` Wouter van Doorn
2017-06-27  8:14     ` Soegtrop, Michael [this message]

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=0F7D3B1B3C4B894D824F5B822E3E5A175B276ED1@IRSMSX102.ger.corp.intel.com \
    --to=michael.soegtrop@intel.com \
    --cc=cygwin@cygwin.com \
    --cc=wouter@vandoorn.tv \
    /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).