From: Andrey Repin <anrdaemon@yandex.ru>
To: Wouter van Doorn <wouter@vandoorn.tv>, cygwin@cygwin.com
Subject: Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
Date: Fri, 23 Jun 2017 00:50:00 -0000 [thread overview]
Message-ID: <412348511.20170623034902@yandex.ru> (raw)
In-Reply-To: <CANZ2p_dgYfAemU55ssSUkJdnX4ALEAFcWtw+h9R_vM4Z-VYzaw@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 1709 bytes --]
Greetings, Wouter van Doorn!
> 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 there:
>>> User-PC-> gdb hello.exe
>>> GNU gdb (GDB) (Cygwin 7.10.1-1) 7.10.1
>> ...
>>> Reading symbols from hello.exe...done.
>>> (gdb) run
>>> Starting program: /home/User/c_dir/hello.exe
>>> [New Thread 6868.0x5b0]
>>> [New Thread 6868.0x18dc]
>>> [New Thread 6868.0x1990]
>>> Hello, world!
>>> [Thread 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?
>>
>> What is "outside"?
>>
>> Are you running this from mintty (recommended) or the Cygwin.bat cmd window?
>>
>> Which shell? (i.e. echo $SHELL)
> With 'outside', I meant a normal run not involving gdb at all. Sorry
> if I was unclear.
> Yes, it's minty, and it's /bin/bash.
> Out of desperation, I have added a sleep for two seconds both before
> and after the printf statement. The sleep does not happen either! The
> prompt is immediately back, so it's more than just 'no output', it
> seems my code never even gets started. Does this shed any new light?
Did you try to rebase your program?
P.S.
And did you try to not top-post in this list? Thank you in advance.
--
With best regards,
Andrey Repin
Friday, June 23, 2017 03:48:14
Sorry for my terrible english...\x03BKCB\x1cØ\x19[H\x1c\^[Ü\x1cÎ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÜ\x1cØ\x19[\Ë\x1d^[[\x03BTN\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÙ\KÃB^[ØÝ[Y[\x18]\x1a[Û\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÙ^[ØÜË\x1d^[[\x03B[ÝXØÜXH\x1a[Î\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÛ[\vÈÝ[ÝXØÜXK\Ú[\^[\x19CBB
next prev parent reply other threads:[~2017-06-23 0:50 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 [this message]
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
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=412348511.20170623034902@yandex.ru \
--to=anrdaemon@yandex.ru \
--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).