From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13715 invoked by alias); 13 Apr 2006 19:49:26 -0000 Received: (qmail 13706 invoked by uid 22791); 13 Apr 2006 19:49:24 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 13 Apr 2006 19:49:23 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id k3DJnLSC028057; Thu, 13 Apr 2006 15:49:21 -0400 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx1.corp.redhat.com (8.12.11.20060308/8.11.6) with ESMTP id k3DJnKYW011749; Thu, 13 Apr 2006 15:49:21 -0400 Received: from [172.16.24.50] (bluegiant.sfbay.redhat.com [172.16.24.50]) by potter.sfbay.redhat.com (8.12.8/8.12.8) with ESMTP id k3DJnITq002597; Thu, 13 Apr 2006 15:49:19 -0400 Message-ID: <443EAB3E.7010006@redhat.com> Date: Thu, 13 Apr 2006 19:49:00 -0000 From: Michael Snyder User-Agent: Mozilla Thunderbird 1.0.7-1.4.1 (X11/20050929) MIME-Version: 1.0 To: Jim Blandy CC: Eli Zaretskii , Jim Blandy , gdb-patches@sources.redhat.com Subject: Re: RFA: Add 'target |' support for MinGW References: <8f2776cb0604130121t4ef6384amd12b6cdc1858c06d@mail.gmail.com> In-Reply-To: <8f2776cb0604130121t4ef6384amd12b6cdc1858c06d@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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/msg00169.txt.bz2 Jim Blandy wrote: > 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! > That should be done explicitly in GDB. Jim's right -- the gdb protocol should be regarded as a binary protocol, even though a lot of it looks like ASCII. We never send text "in the clear". Even when we're simulating stdout, we send the strings encoded. And part of the msg traffic is definitely *not* ascii, so CR/LF conversion would be a very bad thing.