From: Peter Nordstrom <pxno_64@yahoo.com>
To: gdb@sourceware.org
Subject: Re: ARM VFP support
Date: Thu, 28 May 2009 22:36:00 -0000 [thread overview]
Message-ID: <23771374.post@talk.nabble.com> (raw)
In-Reply-To: <23770517.post@talk.nabble.com>
Playing around with the target description files make the assertion go away,
but not able to read anything useful.
Peter Nordstrom wrote:
>
> Yes, target is needed. I'm running on a Marvell Feroceon.
>
> The problem seems to be that mach gets set to bfd_mach_arm_unknown instead
> of bfd_mach_arm_5TE.
>
>
> Daniel Jacobowitz-2 wrote:
>>
>> On Tue, May 19, 2009 at 05:31:48PM -0700, Peter Nordstrom wrote:
>>>
>>> I'm still getting:
>>>
>>> /scratch/maxim/arm-lite/obj-4.3-arm-none-linux-gnueabi-lite/gdb-src-2009q1-176-arm-none-linux-gnueabi-i686-mingw32/gdb/regcache.c:178:
>>> internal-error: register_size: Assertion `regnum >= 0 && regnum <
>>> (gdbarch_num_regs (gdbarch) + gdbarch_num_pseudo_regs (gdbarch))'
>>> failed.
>>>
>>> any ideas?
>>
>> Do you need a target to reproduce this bug? If not, can you send me
>> the binary?
>>
>> --
>> Daniel Jacobowitz
>> CodeSourcery
>>
>>
>
>
--
View this message in context: http://www.nabble.com/ARM-VFP-support-tp22835058p23771374.html
Sent from the Sourceware - gdb list mailing list archive at Nabble.com.
next prev parent reply other threads:[~2009-05-28 22:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 20:25 Matt Fischer
2009-04-01 20:38 ` Daniel Jacobowitz
2009-04-01 20:41 ` Matt Fischer
2009-05-19 23:25 ` Peter Nordstrom
2009-05-19 23:31 ` Daniel Jacobowitz
2009-05-20 0:31 ` Peter Nordstrom
2009-05-20 13:17 ` Daniel Jacobowitz
2009-05-28 21:31 ` Peter Nordstrom
2009-05-28 22:36 ` Peter Nordstrom [this message]
2009-05-29 16:42 ` Peter Nordstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=23771374.post@talk.nabble.com \
--to=pxno_64@yahoo.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox