Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/3] Detect GDB is in cygwin
Date: Tue, 13 Aug 2013 08:12:00 -0000	[thread overview]
Message-ID: <5209EA1F.5040709@codesourcery.com> (raw)
In-Reply-To: <000301ce9408$d51ed560$7f5c8020$@muller@ics-cnrs.unistra.fr>

On 08/08/2013 03:28 PM, Pierre Muller wrote:
>    Without mintty (running Cygwin bash directly), I do get a FILE_TYPE_CHAR,
> and a second check by calling GetConsoleMode with the same handle
> allows to verify that it is indeed a Windows OS Console handle.
>
>    I think that there is indeed no good way to know if we are using
> a non-interactive pipe...
>    As the primary purpose of the patch was to allow better results for the
> testsuite
> for mingw builds, I think that the idea
> of adding a
>   "maint set testsuite-mode on/off"
> command that could be
> automatically added to
> INTERNAL_GDBFLAGS as "-iex {maint set testsuite-mode on}"
> would be a simpler approach.
>    It would guaranty that we do not change existing behavior for
> interactive GDB use and should solve the problem about ^M^M patterns that
> lead to lots of failures when testing mingw builds.
>    As I explained earlier, this changes are also required if you want
> to run the testsuite on msys terminal.
>
>    Should I prepare a RFC?
>

Pierre,
Yes, I think so, but before you post it, we have to coordinate on this. 
  Two people (you and I) post the similar-but-different patches may 
confuse maintainers and doesn't help on review and approval on any
of them.  There are some issues related to mingw and cygwin, and we
(you and I) are working on some of them, with different focus.  If you
don't mind, I'll post my patches again, a fresh version, V4, and
hopefully maintainers can approve them this time.  In the review of V3,
all the questions were addressed, AFAIK, but no one approved it
explicitly.

Then, you can prepare your RFC, and I am happy to help (review and 
test).  Is it OK to you?

>    One question about this new command that I had in mind
> was about the scope of this command.
>    Should I put it inside mingw-hdep.c code and restrict it to
> mingw builds, or should I introduce that command globally,
> the posix-tdep.c version would be an empty function for now,
> but could be useful (?) later.

I prefer the former one.

>    The advantage of the second approach is that we could add
> the "-iex {maint set testsuite-mode on}" unconditionally in gdb.exp,
> but that might seem like a weak argument...

You can modify your board file or build_dir/gdb/testsuite/site.exp to 
append the option to GDBFLAGS.

-- 
Yao (齐尧)


  reply	other threads:[~2013-08-13  8:12 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29  8:46 [PATCH 0/3 V3] Test mingw32 GDB " Yao Qi
2013-07-29  8:46 ` [PATCH 1/3] Detect GDB is " Yao Qi
2013-07-29 15:38   ` Eli Zaretskii
2013-07-30  9:27     ` Yao Qi
2013-07-30 15:33       ` Eli Zaretskii
2013-08-01  7:52         ` Yao Qi
2013-08-01 16:33           ` Eli Zaretskii
2013-08-02  2:51             ` Yao Qi
2013-08-02  6:10               ` Eli Zaretskii
2013-08-03  4:55           ` Christopher Faylor
2013-08-04  8:45             ` Yao Qi
2013-08-05  4:41               ` Christopher Faylor
2013-08-05  6:23                 ` Yao Qi
2013-08-06  2:08                   ` Christopher Faylor
2013-08-06  3:05                     ` Yao Qi
2013-08-08  5:11                       ` Christopher Faylor
2013-08-08  7:24                         ` Yao Qi
2013-08-15 17:40                           ` Christopher Faylor
2013-08-15 18:58                             ` Tom Tromey
2013-08-15 19:14                               ` Eli Zaretskii
2013-08-16  0:06                                 ` Yao Qi
2013-08-16  2:01                                   ` Tom Tromey
2013-08-16  1:07                             ` Yao Qi
2013-08-16 16:37                               ` Christopher Faylor
2013-08-08  7:28                         ` Pierre Muller
2013-08-13  8:12                           ` Yao Qi [this message]
2013-08-13  8:23                             ` Pierre Muller
2013-07-29  8:46 ` [PATCH 2/3] Unbuffer stdout and stderr " Yao Qi
2013-07-29 15:42   ` Eli Zaretskii
2013-08-01  8:06     ` Yao Qi
2013-08-01 16:36       ` Eli Zaretskii
2013-08-02  0:40         ` Yao Qi
2013-07-29  8:46 ` [PATCH 3/3] Set stdin/stdout/stderr to binary mode " Yao Qi
2013-07-29 15:44   ` Eli Zaretskii
2013-08-01  8:10     ` Yao Qi
2013-08-01 16:37       ` Eli Zaretskii
2013-07-29 14:03 ` [PATCH 0/3 V3] Test mingw32 GDB " Pierre Muller
2013-07-30  6:03   ` Yao Qi
2013-07-29 18:03 ` Tom Tromey
2013-07-29 18:43   ` Eli Zaretskii
2013-08-13  9:35 [PATCH 0/3 V4] " Yao Qi
2013-08-13  9:35 ` [PATCH 1/3] Detect GDB is " Yao Qi

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=5209EA1F.5040709@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    /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