From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6386 invoked by alias); 18 Sep 2013 07:20:31 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 6332 invoked by uid 89); 18 Sep 2013 07:20:30 -0000 Received: from mail-ie0-f178.google.com (HELO mail-ie0-f178.google.com) (209.85.223.178) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Wed, 18 Sep 2013 07:20:30 +0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.3 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,NO_RELAYS autolearn=ham version=3.3.2 X-HELO: mail-ie0-f178.google.com Received: by mail-ie0-f178.google.com with SMTP id to1so11694721ieb.23 for ; Wed, 18 Sep 2013 00:20:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=+nGvx3g2O7cR8EfHlV3GVaCFHqSWkOd1bvyhadCtS3I=; b=RLPmWxrYKHzneM5fu/mvFGizOzkh6j5kkN2eLwaE/ubMFWkGV2k9FsXL0WYeGYUxQ5 T5mkoXe6+8HvwSzPMkolE89NcvqmkOZLCM49MXkoevGxJLBX2Bckqvqf7yB2P0zUbhbo u7NAmcJJ0RvhKgbBG+7QlOEfbCZKPvFetfoqkPZajVreH7P0COT3Di4blYc+G/z8U/NW mq3xoimX/tVJunMpw7iWErew2uYWDQo0POu92FO7o9aX9FeovXBBTcmI2mMIOuIFhi11 ybKrGWMBEXqKxi56bppVJNhvotxUyZAnd6oYcIKU2R0ULrvfGW1nJHVREQlwLB2k8vRI Vgpg== X-Gm-Message-State: ALoCoQmmJ4SLcnwTD4b0UgGLYDK5pWdizlkuhdlf2B7jizGXyHrkAuAkg6QEM/4jibplZaVUuf9Mu2uLtj0u21CL6y8Nrus3UvSDRmExFDd8FBVYR4t97XNyfMAoZ5JSmgJpm5/KPN5GgIoJAZ6gfcC2lWoANGXE+EtdQpu0eK/bSPZakx+5NdjUYll4Ait5w03CaLpOVyQfwWSqgP+ernx34a61KkQV+A== MIME-Version: 1.0 X-Received: by 10.43.62.205 with SMTP id xb13mr9086984icb.20.1379488828336; Wed, 18 Sep 2013 00:20:28 -0700 (PDT) Received: by 10.64.31.100 with HTTP; Wed, 18 Sep 2013 00:20:28 -0700 (PDT) In-Reply-To: <20130918021125.GL3132@adacore.com> References: <20130918021125.GL3132@adacore.com> Date: Wed, 18 Sep 2013 07:20:00 -0000 Message-ID: Subject: Re: [RFC] Testsuite: Avoid \r\r\n problem of *-*-mingw* host From: Doug Evans To: Joel Brobecker Cc: Pierre Muller , gdb-patches Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes X-SW-Source: 2013-09/txt/msg00565.txt.bz2 On Tue, Sep 17, 2013 at 7:11 PM, Joel Brobecker 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]