Try the following:
echo $(echo hello | cat)
If that remains empty, (it should of course result in 'hello') you're
suffering from the same problem I have. And no, I did not get it resolved.
In which case I'd be elated if you could get anyone interested in finding a
solution!
If this happens to yo
-when-command-includes-pipes)
but unfortunately that was not resolved. I tried it with virusscanning
switched off - no difference.
Thanks for looking!
Wouter van Doorn
Cygwin Configuration Diagnostics
Current System Time: Tue Aug 08 14:49:03 2017
Windows 7 Professional Ver 6.1 Build 7601 Servic
I bet Comodo is the golden tip. They have introduced whitelisting
without telling anyone, and I have had very strange behaviour (strange
until that whitelist explained it) too. Including that subshell thing.
They call it 'auto-containment'. Just disable that, and done.
Wouter
On 12 July 2017 at 00
No luck with either of the fixed-medium suggestions. The one you
mentioned as default first match on your system is the one I get it
moaning about no matter what I do.
The easiest solution (of sorts) might be to go back to xterm patch
326, but I don't know how to do that either. The installer won'
Thanks, Brian. Your link shows me a page that mentions problems in
xterm-327 through 329, but I have 330, so although the symptom is very
similar, it doesn't seem to be that.
Wouter
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentatio
Hi all,
I have to admit to being almost totally ignorant on fonts under X11.
So not only do I not know how to fix what's happeing (and I found
nothing relevant by searching via google), but I think I also lack the
knowledge to make a mess of it. In fact: I never touched anything to
do with fonts a
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
t bet.
I would like the strace issue to go away, of course, and if someone
has the magic bullet for it I am only too happy to get that issue out
of the way!
Kind regards, and thanks,
Wouter
On 28 June 2017 at 22:02, Vince Rice wrote:
>> On Jun 28, 2017, at 3:00 PM, Wouter van Doorn wrote
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
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
Ho-hum.
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...
I'll have to give up on cygwin, still appreciate the attempts at helping me.
Wouter
--
Problem reports: http://cygwin.com/problems.html
FAQ:
make the
error go away, but I can live with how it is. If developers want me to
run specific tests, I'll be very happy to do so. Otherwise, I'd say we
should consider this closed (but not forgotten).
Thanks again to all who chipped in - it was really apreciated.
Wouter
On 21 June 2
Hello again!
Thanks for your continued support.
Answers to your questions will follow, but I do need to say first that
there has been progress, and although the wy of getting there was
extremely vague, things now do work properly. I'll say more in a
general reply later. So the urgency is gone, bu
Hi René,
There isn't one! The default rule does exactly that (although despite
the -o it creates a hello.exe, but that's fine.
Wouter
I'm convinced that the answer must lie hidden in the two differing
outputs of procmon, elsewhere in this thread. But I lack the knowledge
to go in deeper, and the
Hello Thomas,
Thanks for looking.
The tools are the original ones, as shown below:
User@User-PC ~/c_dir
$ ./hello.exe
User@User-PC ~/c_dir
$ type make
make is hashed (/usr/bin/make)
User@User-PC ~/c_dir
$ type gcc
gcc is /usr/bin/gcc
User@User-PC ~/c_dir
$ type cc
cc is /usr/bin/cc
If you kn
Hi Andrey,
That looked really promising, as that whole rebasing stuff was
something I'd never heard about. Unfortunately, it did not lead to
anything; all my self-compiled tools still do exactly nothing.
Apologies about the top-posting; I had missed that rule.
Wouter
--
Problem reports: ht
Well, it's the same antivirus (comodo) that I earlier had a working
system with, and there's also the matter of it running fine under a
windows command prompt.
Thanks for all your suggestions!
On 22 June 2017 at 17:18, René Berber wrote:
> On 6/22/2017 10:59 AM, Wouter va
immediately back, so it's more than just 'no output', it
seems my code never even gets started. Does this shed any new light?
On 22 June 2017 at 15:08, René Berber wrote:
> On 6/22/2017 8:13 AM, Wouter van Doorn wrote:
>
> [snip]
>> STOP PRESS: in gdb, the output IS
Nice thought, but no, that's not it. The standard utilities behave
normally, only the things I compile myself stay schtumm.
On 22 June 2017 at 14:57, cyg Simple wrote:
>>
>> STOP PRESS: in gdb, the output IS there:
>> User-PC-> gdb hello.exe
>> GNU gdb (GDB) (Cygwin 7.10.1-1) 7.10.1
>> Copyright
6868.0x1990 exited with code 0]
[Inferior 1 (process 6868) exited normally]
(gdb)
Which is dandy, but then why, outside of gdb, is there nothing at all?
Still stumped!
Wouter
On 21 June 2017 at 22:48, René Berber wrote:
> On 6/21/2017 4:10 PM, Wouter van Doorn wrote:
>
>> Having inst
64-bit and 32-bit
libraries being mixed, but as the program runs under the Windows
command prompt, I am discounting that as a reason for the failure.
All the standard pre-compiled utilities I tried run as expected from
the cygwin terminal.
I'd be very grateful for a pointer!
Wouter van Do
21 matches
Mail list logo
