RE: Compile/run problems on cygwin not solved by going to cygwin64

2017-06-29 Thread Soegtrop, Michael
Dear Wouter, great that you found the root cause - I was about to try it on some of my cygwin installation. I would report it as a bug towards the virus scanner manufacturer, that they kill processes without notifying the user. I think users generally want to be informed if the virus scanner t

Re: Compile/run problems on cygwin not solved by going to cygwin64

2017-06-29 Thread Wouter van Doorn
And now, finally, it seems that member Houder managed to nail it! Virusscanner. More specifically: the auto-containment policy of Comodo Antivirus. I've used Comodo for a very long time, certainly from before the moment that they have added that feature, which is essentially a white-list of allow

Re: Compile/run problems on cygwin not solved by going to cygwin64

2017-06-29 Thread Ian Lambert via cygwin
On Wed, 6/28/17, Wouter van Doorn <> wrote: Subject: Compile/run problems on cygwin not solved by going to cygwin64 To: cygwin@cygwin.com Date: Wednesday, June 28, 2017, 4:00 PM == This is what ldd has to say

RE: Compile/run problems on cygwin not solved by going to cygwin64

2017-06-29 Thread Nellis, Kenneth
From: Wouter van Doorn > Hello all, > ... > Attachments: > - cygcheck.out for details of the installation > - installed.db with moreother details of the installation > - PML-files with details of runs as gathered by ProcMon (the 'thread > exit' after closing the file on cygwin1.lib MUST be the clue

Re: Compile/run problems on cygwin not solved by going to cygwin64

2017-06-28 Thread Vince Rice
> On 28 June 2017 at 22:02, Vince Rice wrote: >>> On Jun 28, 2017, at 3:00 PM, Wouter van Doorn wrote: >>> … >>> I can't give the strace output, as 'strace ./hello.exe' causes an >>> immediate segmentation fault. No idea why, but not something I'm going >>> to put energy into right now. >> >> You

Re: Compile/run problems on cygwin not solved by going to cygwin64

2017-06-28 Thread Wouter van Doorn
Hi Vince, If they are related, then solving the problem that's my real current issue will make the strace one go away. If they are not, then I am about to start a second wild goose chase. Sticking with the problem that I am immersed in now in the hope to get that resolved seems to be my best bet.

Re: Compile/run problems on cygwin not solved by going to cygwin64

2017-06-28 Thread Wouter van Doorn
Hi Marco, No difference at all. $ gcc -Wall -o ciao hello.c $ ./ciao $ echo $? 0 $ Am not familiar with the assembler, so I don't know what you were hoping to achieve with that flag, but whatever it was, it didn't do it! Thanks for trying, Wouter -- Problem reports: http://cygwin.com/probl

Re: Compile/run problems on cygwin not solved by going to cygwin64

2017-06-28 Thread Vince Rice
> On Jun 28, 2017, at 3:00 PM, Wouter van Doorn wrote: > … > I can't give the strace output, as 'strace ./hello.exe' causes an > immediate segmentation fault. No idea why, but not something I'm going > to put energy into right now. You should. If strace won't run, you have a problem, and I would b

Re: Compile/run problems on cygwin not solved by going to cygwin64

2017-06-28 Thread Marco Atzeri
On 28/06/2017 22:00, Wouter van Doorn wrote: Hello all, == The Question ==> When I compile a C program, the resulting executable runs fine under the Windows command prompt, but does nothing in the Mintty terminal - any program I compile will terminate immediately and not do anything at all. H

Compile/run problems on cygwin not solved by going to cygwin64

2017-06-28 Thread Wouter van Doorn
Hello all, Recently, I started a thread named 'Compiled programs fail to run from Cygwin Terminal, but work from windows cmd'. I got a lot of angles to look at, but the golden tip wasn't there yet. One advice I had until now laid aside was to use the 64-bit Cygwin version on my 64-bit (Win7) machi