From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Joel Brobecker'" <brobecker@adacore.com>
Cc: "'Doug Evans'" <dje@google.com>,
"'gdb-patches'" <gdb-patches@sourceware.org>
Subject: RE: [RFC] Testsuite: Avoid \r\r\n problem of *-*-mingw* host
Date: Wed, 18 Sep 2013 15:59:00 -0000 [thread overview]
Message-ID: <000c01ceb488$0f892080$2e9b6180$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <20130918134359.GM3132@adacore.com>
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Joel Brobecker
> Envoyé : mercredi 18 septembre 2013 15:44
> À : Pierre Muller
> Cc : 'Doug Evans'; 'gdb-patches'
> Objet : Re: [RFC] Testsuite: Avoid \r\r\n problem of *-*-mingw* host
>
> > > Presumably two difference pieces of software are doing the \n -> \r\n
> > > translation.
> > There is also some \r-> \r\n translation appearing
> > in normal testsuite on any system.
>
> I am wondering if there would be a way to disable that testsuite
> translation in that case...
Maybe we could use this
http://www.tcl.tk/man/tcl8.0/TclCmd/fconfigure.htm
But I still did not understand how it really works,
nor did I really find to which channel I should apply
this so that mingw host GDB's output is handled correctly.
Maybe someone else on the list knows more about this
tcl command and how it could be used for our problem!
Pierre Muller
next prev parent reply other threads:[~2013-09-18 15:59 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
2013-09-18 7:33 ` Pierre Muller
2013-09-18 13:44 ` Joel Brobecker
2013-09-18 15:59 ` Pierre Muller [this message]
[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='000c01ceb488$0f892080$2e9b6180$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--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