From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32523 invoked by alias); 29 Nov 2001 16:04:53 -0000 Mailing-List: contact gdb-help@sourceware.cygnus.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 31799 invoked from network); 29 Nov 2001 16:03:34 -0000 Received: from unknown (HELO gash2.peakpeak.com) (207.174.178.17) by hostedprojects.ges.redhat.com with SMTP; 29 Nov 2001 16:03:34 -0000 Received: from creche.cygnus.com (ta0205.peakpeak.com [204.144.244.205]) by gash2.peakpeak.com (8.9.3/8.9.3) with ESMTP id JAA06399; Thu, 29 Nov 2001 09:01:49 -0700 Received: (from tromey@localhost) by creche.cygnus.com (8.9.3/8.9.3) id JAA27670; Thu, 29 Nov 2001 09:04:12 -0700 To: Eli Zaretskii Cc: Klaus-Georg Adams , gdb@sources.redhat.com Subject: Re: displaying wchar_t in gdb References: X-Zippy: YOW!! What should the entire human race DO?? Consume a fifth of CHIVAS REGAL, ski NUDE down MT. EVEREST, and have a wild SEX WEEKEND! X-Attribution: Tom Reply-To: tromey@redhat.com From: Tom Tromey Date: Sat, 24 Nov 2001 22:42:00 -0000 In-Reply-To: Eli Zaretskii's message of "Thu, 29 Nov 2001 10:18:43 +0200 (IST)" Message-ID: <87k7w9d0n8.fsf@creche.redhat.com> X-Mailer: Gnus v5.7/Emacs 20.5 X-SW-Source: 2001-11/txt/msg00230.txt.bz2 >>>>> "Eli" == Eli Zaretskii writes: Eli> Risky assumptions, both of them (IMHO). For example, GDB can be Eli> conceivably built with libiconv, but you cannot force the Eli> debuggee to be built with it. I don't think the debuggee would need iconv. GDB would fetch raw bytes from the inferior, and then transform them to the appropriate output encoding using the host iconv. >> For wchar_t I don't think you need a new `print' format (well maybe to >> specify the encoding). I think a wchar_t string could be printed >> based solely on the type, the way we print a char* string right now. Eli> I think you need a format because a buffer can be declared Eli> `unsigned char *' even though it holds wide characters. There's always `p (wchar_t *) buf'. I already use this idiom with ordinary char* strings on occasion. Tom From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Tromey To: Eli Zaretskii Cc: Klaus-Georg Adams , gdb@sources.redhat.com Subject: Re: displaying wchar_t in gdb Date: Thu, 29 Nov 2001 08:04:00 -0000 Message-ID: <87k7w9d0n8.fsf@creche.redhat.com> References: X-SW-Source: 2001-11/msg00337.html Message-ID: <20011129080400.RXxH5sHW00pUt3NW3RJUOdXrnyiOVS8Ay_X2dnMjmQ8@z> >>>>> "Eli" == Eli Zaretskii writes: Eli> Risky assumptions, both of them (IMHO). For example, GDB can be Eli> conceivably built with libiconv, but you cannot force the Eli> debuggee to be built with it. I don't think the debuggee would need iconv. GDB would fetch raw bytes from the inferior, and then transform them to the appropriate output encoding using the host iconv. >> For wchar_t I don't think you need a new `print' format (well maybe to >> specify the encoding). I think a wchar_t string could be printed >> based solely on the type, the way we print a char* string right now. Eli> I think you need a format because a buffer can be declared Eli> `unsigned char *' even though it holds wide characters. There's always `p (wchar_t *) buf'. I already use this idiom with ordinary char* strings on occasion. Tom