From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26881 invoked by alias); 19 Nov 2008 13:31:41 -0000 Received: (qmail 26873 invoked by uid 22791); 19 Nov 2008 13:31:40 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 19 Nov 2008 13:31:00 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id EF16C10A09; Wed, 19 Nov 2008 13:30:58 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id D0A2E10A06; Wed, 19 Nov 2008 13:30:56 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1L2n8y-0005Kq-CC; Wed, 19 Nov 2008 08:30:56 -0500 Date: Wed, 19 Nov 2008 13:31:00 -0000 From: Daniel Jacobowitz To: Sergei Poselenov Cc: gdb@sources.redhat.com Subject: Re: ARM EABI: GDB internal error on printing out float (VFP math) Message-ID: <20081119133056.GA20492@caradoc.them.org> Mail-Followup-To: Sergei Poselenov , gdb@sources.redhat.com References: <491C3ACE.2050201@emcraft.com> <20081113145102.GA10827@caradoc.them.org> <4923EBE5.6050900@emcraft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4923EBE5.6050900@emcraft.com> User-Agent: Mutt/1.5.17 (2008-05-11) 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: 2008-11/txt/msg00122.txt.bz2 On Wed, Nov 19, 2008 at 01:35:17PM +0300, Sergei Poselenov wrote: > Thanks for the answer. > > So, it turns out that GDB is unusable with VFP-enabled applications? I'm not sure about the error you got. I use GDB with VFP code all the time, but I don't think I've ever seen that error. > Do you happen to know any workarounds, or plans to fix this in ARM > kernel and in GDB? Yes, there are plans to fix this. I don't know when it will be ready, though. -- Daniel Jacobowitz CodeSourcery