From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-39544-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 4048 invoked by alias); 18 Jul 2011 09:06:06 -0000
Received: (qmail 4039 invoked by uid 22791); 18 Jul 2011 09:06:05 -0000
X-SWARE-Spam-Status: No, hits=-7.0 required=5.0	tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS
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; Mon, 18 Jul 2011 09:05:48 +0000
Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11])	by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p6I95jTk015377	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);	Mon, 18 Jul 2011 05:05:45 -0400
Received: from hase.home (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1])	by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p6I95h1p001947;	Mon, 18 Jul 2011 05:05:44 -0400
From: Andreas Schwab <schwab@redhat.com>
To: Xingxing Pan <forandom@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: gdbserver error message
References: <CANB_ExmpjHK6VHadJWrRZ43hA4ynJx-SSFEKmdnOhBo-BF6Zgw@mail.gmail.com>
X-Yow: I'm having an emotional outburst!!
Date: Mon, 18 Jul 2011 09:06:00 -0000
In-Reply-To: <CANB_ExmpjHK6VHadJWrRZ43hA4ynJx-SSFEKmdnOhBo-BF6Zgw@mail.gmail.com>	(Xingxing Pan's message of "Mon, 18 Jul 2011 16:54:20 +0800")
Message-ID: <m3y5zwx8k8.fsf@hase.home>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2011-07/txt/msg00082.txt.bz2

Xingxing Pan <forandom@gmail.com> writes:

> Error message from debugger back end:
> 192.168.20.239:2345: \350\277\236\346\216\245\350\266\205\346\227\266.
> 192.168.20.239:2345: \350\277\236\346\216\245\350\266\205\346\227\266.
>
> The error message is unreadable. Dose anyone know how is the error
> message encoded?

Looks like some chinese in UTF-8.

ELISP> (detect-coding-string  "\350\277\236\346\216\245\350\266\205\346\227=
\266")
(utf-8 japanese-shift-jis raw-text utf-8-auto utf-16be utf-16le)
ELISP> (decode-coding-string "\350\277\236\346\216\245\350\266\205\346\227\=
266" 'utf-8)
"=E8=BF=9E=E6=8E=A5=E8=B6=85=E6=97=B6"

Andreas.

--=20
Andreas Schwab, schwab@redhat.com
GPG Key fingerprint =3D D4E8 DBE3 3813 BB5D FA84  5EC7 45C6 250E 6F00 984E
"And now for something completely different."