From: Joel Brobecker <brobecker@adacore.com>
To: gdb@sources.redhat.com
Subject: Re: MinGW gdb run in non-DOS terminal
Date: Mon, 01 May 2006 17:22:00 -0000 [thread overview]
Message-ID: <20060501172216.GE936@adacore.com> (raw)
In-Reply-To: <20060501171137.GA7482@nevyn.them.org>
> It is roughly unsolvable. A cygwin "terminal" is in fact a Windows
> pipe; isatty() returns false, therefore the C library selects
> line-buffered mode, which is a pretty standard thing for C runtimes
> to do.
:-(. In fact, I see the same in GPS where cygwin is nowhere in sight.
> I suppose that if the CLI is in use, you could automatically turn off
> buffering. But there may be plenty of other problems...
Maybe we should start with that. Would you mind pointing me in the
area where this should be done? I can experiment with that and see
if we have any other obvious problems.
--
Joel
next prev parent reply other threads:[~2006-05-01 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 17:05 Joel Brobecker
2006-05-01 17:11 ` Daniel Jacobowitz
2006-05-01 17:22 ` Joel Brobecker [this message]
2006-05-01 17:30 ` Daniel Jacobowitz
2006-05-01 18:18 ` Joel Brobecker
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=20060501172216.GE936@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sources.redhat.com \
/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