From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1251 invoked by alias); 13 Apr 2006 08:21:08 -0000 Received: (qmail 1242 invoked by uid 22791); 13 Apr 2006 08:21:07 -0000 X-Spam-Check-By: sourceware.org Received: from xproxy.gmail.com (HELO xproxy.gmail.com) (66.249.82.198) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 13 Apr 2006 08:21:06 +0000 Received: by xproxy.gmail.com with SMTP id h29so1106164wxd for ; Thu, 13 Apr 2006 01:21:03 -0700 (PDT) Received: by 10.70.118.11 with SMTP id q11mr296380wxc; Thu, 13 Apr 2006 01:21:01 -0700 (PDT) Received: by 10.70.125.5 with HTTP; Thu, 13 Apr 2006 01:21:01 -0700 (PDT) Message-ID: <8f2776cb0604130121t4ef6384amd12b6cdc1858c06d@mail.gmail.com> Date: Thu, 13 Apr 2006 08:21:00 -0000 From: "Jim Blandy" To: "Eli Zaretskii" Subject: Re: RFA: Add 'target |' support for MinGW Cc: "Jim Blandy" , gdb-patches@sources.redhat.com In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-04/txt/msg00165.txt.bz2 On 4/13/06, Eli Zaretskii wrote: > > Cc: gdb-patches@sources.redhat.com > > From: Jim Blandy > > Date: Wed, 12 Apr 2006 11:38:55 -0700 > > > > > Do we really want binary I/O in _all_ situations? Can it be that, > > > depending on the command on the other side of the pipe, someone would > > > like the CR characters to be stripped from the EOLs in the incoming > > > stuff? The way you wrote it, AFAICS, binary I/O is always used, no > > > matter what. > > > > Well, the pipe is carrying the GDB remote protocol, which is happier > > with binary. > > Do we never ask the remote to list text files, for example? No, we don't. Text is always encoded in hex, to avoid any munging of this sort. And for goodness' sake, we wouldn't want line ending conversion happening magically in the protocol's transport layer!=20 That should be done explicitly in GDB.