From: Daniel Jacobowitz <drow@false.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: Denis PILAT <denis.pilat@st.com>, Eli Zaretskii <eliz@gnu.org>,
gdb-patches@sourceware.org
Subject: Re: '\r' only end-of-line
Date: Wed, 11 Oct 2006 15:05:00 -0000 [thread overview]
Message-ID: <20061011150501.GA28355@nevyn.them.org> (raw)
In-Reply-To: <452D02BE.30502@st.com>
On Wed, Oct 11, 2006 at 03:42:06PM +0100, Andrew STUBBS wrote:
> Daniel Jacobowitz wrote:
> >I am pretty sure you'll get nasty lossage from, e.g., GDB thinking it's
> >not connected to a terminal. Error messages will show up after
> >prompts, and questions will be suppressed.
>
> Yes, in the absence of a better solution, we have gdb_has_a_terminal
> always return 1 for MinGW. It means that it doesn't work right for
> pipes, but without this it does not work right in normal interactive
> mode, which is worse.
>
> As far as I am aware this is a normal MinGW problem, not limited to use
> with Expect.
It works fine in a Windows command shell without this, which is how we
currently use it.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-11 15:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 15:25 [TUI] correctly display windows source files Denis PILAT
2006-10-09 18:01 ` Mark Kettenis
2006-10-09 19:28 ` Eli Zaretskii
2006-10-10 13:23 ` Denis PILAT
2006-10-10 15:08 ` '\r' only end-of-line Denis PILAT
2006-10-10 21:34 ` Eli Zaretskii
2006-10-11 10:08 ` Denis PILAT
2006-10-11 13:33 ` Daniel Jacobowitz
2006-10-11 13:57 ` Andrew STUBBS
2006-10-11 14:01 ` Daniel Jacobowitz
2006-10-11 14:44 ` Andrew STUBBS
2006-10-11 15:05 ` Daniel Jacobowitz [this message]
2006-10-11 17:47 ` Eli Zaretskii
2006-10-11 17:36 ` Eli Zaretskii
2006-10-16 8:51 ` Denis PILAT
2006-10-10 21:24 ` [TUI] correctly display windows source files Eli Zaretskii
2006-10-11 8:02 ` Denis PILAT
2006-10-11 8:39 ` Eli Zaretskii
2006-10-11 11:23 ` Frederic RISS
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=20061011150501.GA28355@nevyn.them.org \
--to=drow@false.org \
--cc=andrew.stubbs@st.com \
--cc=denis.pilat@st.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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