Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>, Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Building the 7.8.90 pretest on MinGW
Date: Thu, 22 Jan 2015 11:05:00 -0000	[thread overview]
Message-ID: <54C0D965.9000305@redhat.com> (raw)
In-Reply-To: <83lhkyy84l.fsf@gnu.org>

Sorry for the delay.

On 01/19/2015 05:48 PM, Eli Zaretskii wrote:

> Thanks.  I'd like to hear from Pedro as well, as the changes which
> caused this were committed by him.

This is OK with me.

A couple questions though:

The "cup" check is there to make sure that e.g., starting GDB
in a shell within emacs doesn't result in a messed up session.
Did you try that?  I imagine that cases like when stdin is a
pipe, like e.g., when starting mingw gdb in a cygwin shell
or in a cygwin ssh session, may result in a messed up screen.

I mildly wonder whether pdcurses works here as is without
this patch, thus whether the #ifdef check should distinguish
ncurses from pdcurses somehow.  IIUC, some people build with
pdcurses instead of GNU ncurses.

Thanks,
Pedro Alves


  reply	other threads:[~2015-01-22 11:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <announce.20150113122445.36DDE48E8A@joel.gnat.com>
2015-01-15 16:07 ` Eli Zaretskii
2015-01-15 19:49   ` Doug Evans
2015-01-19 17:48     ` Eli Zaretskii
2015-01-22 11:05       ` Pedro Alves [this message]
2015-01-22 16:09         ` Eli Zaretskii
2015-01-22 17:04           ` Pedro Alves
2015-01-22 17:27             ` Eli Zaretskii
2015-01-22 17:46               ` Pedro Alves
2015-01-22 18:30           ` Eli Zaretskii
2015-01-16  8:49   ` Eli Zaretskii
2015-01-20 18:27     ` Joel Brobecker
2015-01-20 18:36       ` Eli Zaretskii
2015-01-20 19:08         ` 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=54C0D965.9000305@redhat.com \
    --to=palves@redhat.com \
    --cc=dje@google.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