From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18410 invoked by alias); 23 Dec 2011 20:10:27 -0000 Received: (qmail 18401 invoked by uid 22791); 23 Dec 2011 20:10:24 -0000 X-SWARE-Spam-Status: No, hits=-7.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS,TW_XG X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 23 Dec 2011 20:10:07 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id pBNKA6P1003023 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 23 Dec 2011 15:10:06 -0500 Received: from host2.jankratochvil.net (ovpn-116-60.ams2.redhat.com [10.36.116.60]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id pBNK9qbo023884 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 23 Dec 2011 15:09:58 -0500 Date: Sat, 24 Dec 2011 01:55:00 -0000 From: Jan Kratochvil To: xgsa Cc: Tom Tromey , gdb-patches@sourceware.org Subject: Re: set print object on should affect MI varobjs (PR mi/13393) Message-ID: <20111223200951.GA19581@host2.jankratochvil.net> References: <4ED92C05.9080803@yandex.ru> <4EF22A4D.80703@yandex.ru> <20111221193630.GA28985@host2.jankratochvil.net> <4EF30389.5010008@yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4EF30389.5010008@yandex.ru> User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes 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 X-SW-Source: 2011-12/txt/msg00814.txt.bz2 On Thu, 22 Dec 2011 11:16:41 +0100, xgsa wrote: > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > The updated ChangeLog & patch after Jan's review fixture. Could you please use either a different mail client or if not possible then at least to attach the patch as file? The "flowed" format corrupts it a lot, I do not know where are which spaces, for example I guess your ChangeLog entry exceeds 80 characters as 8 initial characters is tab. And I cannot apply the patch, with both rfc822 text or decoded body I get: patching file gdb/c-valprint.c Hunk #1 FAILED at 698. 1 out of 1 hunk FAILED -- saving rejects to file gdb/c-valprint.c.rej patching file gdb/eval.c patch: **** malformed patch at line 86: && (TYPE_CODE (TYPE_TARGET_TYPE (type)) == TYPE_CODE_CLASS)) Sorry for the hassle. Thanks, Jan