From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14173 invoked by alias); 17 Oct 2012 14:58:25 -0000 Received: (qmail 14152 invoked by uid 22791); 17 Oct 2012 14:58:23 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_HOSTKARMA_NO X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 17 Oct 2012 14:58:16 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id C76F11C6DFC; Wed, 17 Oct 2012 10:58:15 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id DjYPwYP1F+gT; Wed, 17 Oct 2012 10:58:15 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id E1B741C6FFA; Wed, 17 Oct 2012 10:58:13 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 8E278C4B88; Wed, 17 Oct 2012 07:58:06 -0700 (PDT) Date: Wed, 17 Oct 2012 14:58:00 -0000 From: Joel Brobecker To: Tom Tromey Cc: gdb-patches@sourceware.org Subject: Re: printing 0xbeef wchar_t on x86-windows... Message-ID: <20121017145806.GK3050@adacore.com> References: <20121015190052.GH3034@adacore.com> <87wqyq6tcl.fsf@fleche.redhat.com> <20121016224342.GH3050@adacore.com> <87fw5d7uck.fsf@fleche.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87fw5d7uck.fsf@fleche.redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) 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: 2012-10/txt/msg00273.txt.bz2 > Tom> Before putting something like that in, though, I would like to look at > Tom> Keith's pending patch that reworks this code. Maybe he already fixed > Tom> the bug. > > http://sourceware.org/ml/gdb-patches/2012-08/msg00780.html Thanks! I gave it a whirl, JIC, and as you suspected, it does not fix the 0xdeadbeef issue on Windows. It looks like a nice improvement, however - with maybe one comment which I will send by replying to the email... -- Joel