Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>,
		gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [RFC] Testsuite: Avoid \r\r\n problem of *-*-mingw* host
Date: Wed, 18 Sep 2013 07:20:00 -0000	[thread overview]
Message-ID: <CADPb22S9V2UM-2FA=0QPhe1bp38HxSuXU4xFy83DgDPWfsmQpQ@mail.gmail.com> (raw)
In-Reply-To: <20130918021125.GL3132@adacore.com>

On Tue, Sep 17, 2013 at 7:11 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>>   Here is an alternate proposal to get rid of that double \r
>> problem encountered when running the testsuite with mingw host GDB.
>>
>>   maint set testsuite-mode on
>> force stdout and stderr to use binary mode.
>>
>>   maint set testsuite-mode off
>> restores stdout and stderr "normal" text mode behavior.
>
> FWIW, I tend to think that it's better to test the debugger in
> an environment that is as close as possible to reality. For
> those reasons, I tend to favor Yao's approach.  But it's not
> a strong opinion.

Can someone explain how \r\r\n occurs?
Presumably two difference pieces of software are doing the \n -> \r\n
translation.
What are they?

[hacking the testsuite may be preferable in some way, but I'm worried
that road will be long and painful]


  reply	other threads:[~2013-09-18  7:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-17 23:14 Pierre Muller
2013-09-18  2:11 ` Joel Brobecker
2013-09-18  7:20   ` Doug Evans [this message]
2013-09-18  7:33     ` Pierre Muller
2013-09-18 13:44       ` Joel Brobecker
2013-09-18 15:59         ` Pierre Muller
     [not found]         ` <5239cde9.0db6b40a.21be.fffff5f5SMTPIN_ADDED_BROKEN@mx.google.com>
2013-09-18 17:14           ` Doug Evans

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='CADPb22S9V2UM-2FA=0QPhe1bp38HxSuXU4xFy83DgDPWfsmQpQ@mail.gmail.com' \
    --to=dje@google.com \
    --cc=brobecker@adacore.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