From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23986 invoked by alias); 14 Apr 2006 13:43:09 -0000 Received: (qmail 23978 invoked by uid 22791); 14 Apr 2006 13:43:09 -0000 X-Spam-Check-By: sourceware.org Received: from sadr.equallogic.com (HELO sadr.equallogic.com) (66.155.203.134) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 14 Apr 2006 13:43:06 +0000 Received: from sadr.equallogic.com (localhost.localdomain [127.0.0.1]) by sadr.equallogic.com (8.12.8/8.12.8) with ESMTP id k3EDh4kq020446 for ; Fri, 14 Apr 2006 09:43:04 -0400 Received: from M31.equallogic.com (M31.equallogic.com [172.16.1.31]) by sadr.equallogic.com (8.12.8/8.12.8) with SMTP id k3EDh33L020441; Fri, 14 Apr 2006 09:43:03 -0400 Received: from pkoning.equallogic.com ([172.16.1.169]) by M31.equallogic.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 14 Apr 2006 09:43:03 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17471.42725.651176.368871@gargle.gargle.HOWL> Date: Fri, 14 Apr 2006 14:08:00 -0000 From: Paul Koning To: eliz@gnu.org Cc: ghost@cs.msu.su, gdb@sources.redhat.com Subject: Re: printing wchar_t* References: X-Mailer: VM 7.17 under 21.5 (beta23) "daikon" XEmacs Lucid X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-04/txt/msg00187.txt.bz2 >>>>> "Eli" == Eli Zaretskii writes: >> From: Vladimir Prus Date: Fri, 14 Apr 2006 >> 10:01:57 +0400 >> >> > What character set is used by the wide characters in the wchar_t >> > arrays? GDB has some support for a few single-byte character >> sets, > see the node "Character Sets" in the manual. >> >> Relatively safe bet would be to assume it's some zero-terminated >> character set. I plan to assume it's either UTF-16 or UTF-32 in >> the GUI (the conversion code is the same for both encodings), but >> gdb can just print raw values. Eli> We should get our terminology right: UTF-16 is not a character Eli> set, it's an encoding (and a multibyte encoding, btw). As for Eli> UTF-32, I don't think such a beast exists at all. I seem to remember seeing it mentioned. It certainly makes sense. Eli> I think you meant 16-bit Unicode characters (a.k.a. the BMP) and Eli> 32-bit Unicode characters, respectively. If you have 16 bit wide chars, it seems possible that those might contain UTF-16 encoding of full (beyond BMP) Unicode characters. paul