From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21514 invoked by alias); 27 Sep 2010 10:25:47 -0000 Received: (qmail 21435 invoked by uid 22791); 27 Sep 2010 10:25:45 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Received: from mail-ey0-f169.google.com (HELO mail-ey0-f169.google.com) (209.85.215.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 27 Sep 2010 10:25:40 +0000 Received: by eyh5 with SMTP id 5so1512376eyh.0 for ; Mon, 27 Sep 2010 03:25:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.213.62.206 with SMTP id y14mr2848746ebh.34.1285583138328; Mon, 27 Sep 2010 03:25:38 -0700 (PDT) Received: by 10.213.29.201 with HTTP; Mon, 27 Sep 2010 03:25:38 -0700 (PDT) In-Reply-To: <201009241539.35561.pedro@codesourcery.com> References: <201009241405.o8OE5BMx026432@d12av02.megacenter.de.ibm.com> <201009241539.35561.pedro@codesourcery.com> Date: Mon, 27 Sep 2010 10:25:00 -0000 Message-ID: Subject: Re: gdbserver 7.1 unable to read registers From: Steffen Dettmer To: gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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: 2010-09/txt/msg00150.txt.bz2 On Fri, Sep 24, 2010 at 4:39 PM, Pedro Alves wrote: > On the other hand, there's scope for improvement in those warnings. > It's not surprising that users don't know the consequences of not > being able to parse a "XML target description" are. =A0Making > those clearer in terms of consequences would probably already > go a long way in avoiding surprises. =A0Something along the lines > of: > > =A0"Can not parse XML target description; XML support was > disabled at compile time." > =A0"GDB may not be able to read registers correctly." Yes, at least for me I never guessed that XML support is needed to read registers... BTW, where can I learn more why XML is suited and needed to read registers? XML remembers me to complex stuff like parsers needing 10 MB source code, Unicode with chinese characters, OpenOffice documents... I do not see an XML warning message when gdb tries to connect, but I have a problem with "call" in remote debugging (arm-elf-nonlinux-gdb-7.20): (gdb) p strlen("") Could not write register "cpsr"; remote failure reply 'E00' An error occurred while in a function called from GDB. Evaluation of the expression containing the function (malloc) will be abandoned. When the function is done executing, GDB will silently stop. Could this be caused by missing expat support, or would I definitely see a XML warning message in case? oki, Steffen