From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7144 invoked by alias); 24 Sep 2010 13:44:42 -0000 Received: (qmail 7135 invoked by uid 22791); 24 Sep 2010 13:44:41 -0000 X-SWARE-Spam-Status: No, hits=-0.7 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from mail.carallon.com (HELO mail.carallon.com) (95.177.28.122) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 24 Sep 2010 13:44:36 +0000 X-MDAV-Processed: mail.carallon.com, Fri, 24 Sep 2010 14:44:34 +0100 Received: from [192.168.1.10] by mail.carallon.com (Cipher TLSv1:-SHA:128) (MDaemon PRO v11.0.3) with ESMTP id md50000632142.msg for ; Fri, 24 Sep 2010 14:44:33 +0100 X-Spam-Processed: mail.carallon.com, Fri, 24 Sep 2010 14:44:33 +0100 (not processed: message from trusted or authenticated source) X-MDRemoteIP: 81.174.245.187 X-Return-Path: will_wagner@carallon.com X-Envelope-From: will_wagner@carallon.com X-MDaemon-Deliver-To: gdb@sourceware.org Message-ID: <4C9CAB33.8010708@carallon.com> Date: Fri, 24 Sep 2010 13:44:00 -0000 From: William Wagner User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: Pedro Alves CC: gdb@sourceware.org, Ulrich Weigand Subject: Re: gdbserver 7.1 unable to read registers References: <201009241258.o8OCw8Sx024740@d12av02.megacenter.de.ibm.com> <201009241436.00567.pedro@codesourcery.com> In-Reply-To: <201009241436.00567.pedro@codesourcery.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: 2010-09/txt/msg00131.txt.bz2 On 24/09/2010 14:36, Pedro Alves wrote: > On Friday 24 September 2010 13:58:08, Ulrich Weigand wrote: > >> Usually, gdbserver will inform GDB via the remote protocol about the >> set of registers supported on the platform, and GDB is supposed to >> automatically take that information into account. >> >> However, this requires that GDB is built to include XML support to >> parse this configuration information; if the expat libraries were >> not available when you built GDB, the configure process might have >> decided to build GDB without XML support instead ... >> Can you try rebuilding with the --with-expat configure option? >> This will cause the build to fail if XML support is not available. > Note that GDB issues a warning at connect time in that case: > > "Can not parse XML target description; XML support was disabled at compile time" When I run gdb I see that warning, did not realise what the consequence of not having XML support was. Will recompile with expat and see if that fixes it. Thanks everyone for the help. Will -- ------------------------------------------------------------------------ Will Wagner will_wagner@carallon.com Development Manager Office Tel: +44 (0)20 7371 2032 Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA ------------------------------------------------------------------------