From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17717 invoked by alias); 25 Feb 2007 19:54:20 -0000 Received: (qmail 17709 invoked by uid 22791); 25 Feb 2007 19:54:18 -0000 X-Spam-Check-By: sourceware.org Received: from 195.22.55.53.adsl.nextra.cz (HELO host0.dyn.jankratochvil.net) (195.22.55.53) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 25 Feb 2007 19:54:09 +0000 Received: from host0.dyn.jankratochvil.net (localhost [127.0.0.1]) by host0.dyn.jankratochvil.net (8.14.0/8.13.8) with ESMTP id l1PJrrEa012844; Sun, 25 Feb 2007 20:53:54 +0100 Received: (from jkratoch@localhost) by host0.dyn.jankratochvil.net (8.14.0/8.14.0/Submit) id l1PJroYO012843; Sun, 25 Feb 2007 20:53:50 +0100 Date: Mon, 26 Feb 2007 00:45:00 -0000 From: Jan Kratochvil To: mathieu lacage Cc: Nick Roberts , Daniel Jacobowitz , gdb@sourceware.org Subject: Re: [RFC] Signed/unsigned character arrays are not strings Message-ID: <20070225195350.GA12811@host0.dyn.jankratochvil.net> References: <17887.62990.937672.281975@kahikatea.snap.net.nz> <20070224161315.GA27534@caradoc.them.org> <17888.39894.136355.447008@kahikatea.snap.net.nz> <1172390381.2584.18.camel@mathieu> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="UugvWAfsgieZRqgk" Content-Disposition: inline In-Reply-To: <1172390381.2584.18.camel@mathieu> User-Agent: Mutt/1.5.13 (2007-02-12) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-02/txt/msg00263.txt.bz2 --UugvWAfsgieZRqgk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-length: 464 On Sun, 25 Feb 2007 08:59:41 +0100, mathieu lacage wrote: ... > I don't know how useful that is to you but a lot of people (the first > which comes to my mind is libxml2) decided to use "unsigned char *" to > identify utf-8 encoded strings in C. Together with the attached RMS's response I became more inclined to revert this change and provide only "$xmm"-specific fix instead (probably for the GDB int8_t/uint8_t internal types). OK to submit the patch? Jan --UugvWAfsgieZRqgk Content-Type: message/rfc822 Content-Disposition: inline Content-length: 2430 Return-Path: Received: from localhost by host0.dyn.jankratochvil.net with IMAP (fetchmail-6.3.6) for (single-drop); Sun, 25 Feb 2007 20:32:23 +0100 (CET) Received: from pobox.stuttgart.redhat.com ([unix socket]) by pobox.stuttgart.redhat.com (Cyrus v2.1.12) with LMTP; Sun, 25 Feb 2007 20:32:05 +0100 X-Sieve: CMU Sieve 2.2 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by pobox.stuttgart.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id l1PJW4JQ022731 for ; Sun, 25 Feb 2007 20:32:04 +0100 Received: from mx2.redhat.com (mx2.redhat.com [10.255.15.25]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l1PJW3n7019101 for ; Sun, 25 Feb 2007 14:32:03 -0500 Received: from fencepost.gnu.org (fencepost.gnu.org [199.232.76.164]) by mx2.redhat.com (8.13.1/8.13.1) with ESMTP id l1PJW1g9011807 for ; Sun, 25 Feb 2007 14:32:02 -0500 Received: from rms by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1HLP4h-0003js-7j; Sun, 25 Feb 2007 14:30:23 -0500 Content-Type: text/plain; charset=ISO-8859-15 From: Richard Stallman To: Nick Roberts CC: jan.kratochvil@redhat.com cc: bug-gdb@gnu.org In-reply-to: <17889.3323.360519.26769@kahikatea.snap.net.nz> (message from Nick Roberts on Sun, 25 Feb 2007 17:13:47 +1300) Subject: Re: Emacs .gdbinit incompatible with latest GDB Reply-to: rms@gnu.org References: <200702242133.l1OLXKff004169@host0.dyn.jankratochvil.net> <17889.3323.360519.26769@kahikatea.snap.net.nz> Message-Id: Date: Sun, 25 Feb 2007 14:30:23 -0500 X-RedHat-Spam-Score: -1.44 Content-length: 665 the recent GDB has problems running GDB `xbacktrace' on EMACS http://sources.redhat.com/ml/gdb/2007-02/msg00252.html It seems clear why the change was made: On the other hand byte arrays become unreadable if printed as strings. However, it seems that their hope this would not bother anyone was based on an assumption which is inaccurate: I hope nobody uses sign-specification for strings. Which GDB behavior is better is a matter of how often each one is convenient and how often it causes trouble. I don't know enough to have an opinion about that, but if neither one is clearly better overall, it would be best to leave GDB the way it was. --UugvWAfsgieZRqgk Content-Type: message/rfc822 Content-Disposition: inline Content-length: 2116 Return-Path: Received: from localhost by host0.dyn.jankratochvil.net with IMAP (fetchmail-6.3.6) for (single-drop); Sun, 25 Feb 2007 20:33:04 +0100 (CET) Received: from pobox.stuttgart.redhat.com ([unix socket]) by pobox.stuttgart.redhat.com (Cyrus v2.1.12) with LMTP; Sun, 25 Feb 2007 20:32:06 +0100 X-Sieve: CMU Sieve 2.2 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by pobox.stuttgart.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id l1PJW4NK022732 for ; Sun, 25 Feb 2007 20:32:05 +0100 Received: from mx2.redhat.com (mx2.redhat.com [10.255.15.25]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l1PJW3v7019103 for ; Sun, 25 Feb 2007 14:32:04 -0500 Received: from fencepost.gnu.org (fencepost.gnu.org [199.232.76.164]) by mx2.redhat.com (8.13.1/8.13.1) with ESMTP id l1PJW2l1011868 for ; Sun, 25 Feb 2007 14:32:03 -0500 Received: from rms by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1HLP4i-0003k4-IF; Sun, 25 Feb 2007 14:30:24 -0500 Content-Type: text/plain; charset=ISO-8859-15 From: Richard Stallman To: Nick Roberts CC: jan.kratochvil@redhat.com, emacs-pretest-bug@gnu.org In-reply-to: <17889.3323.360519.26769@kahikatea.snap.net.nz> (message from Nick Roberts on Sun, 25 Feb 2007 17:13:47 +1300) Subject: Re: Emacs .gdbinit incompatible with latest GDB Reply-to: rms@gnu.org References: <200702242133.l1OLXKff004169@host0.dyn.jankratochvil.net> <17889.3323.360519.26769@kahikatea.snap.net.nz> Message-Id: Date: Sun, 25 Feb 2007 14:30:24 -0500 X-RedHat-Spam-Score: -1.44 Content-length: 344 2000-01-04 Gerd Moellmann * lisp.h (struct Lisp_String): Make DATA member `unsigned char *'. I guess the questions to ask are: 1) Why was this change made? Probably to make it easier to avoid incorrect conversions when extracting elements. We don't want to get negative numbers for byte values above 127. --UugvWAfsgieZRqgk--