From: Pedro Alves <palves@redhat.com>
To: Peter Balazovic <balazovic.peter@gmail.com>, gdb@sourceware.org
Subject: Re: gdbserver: Target description specified unknown architecture “aarch64”
Date: Thu, 29 Nov 2018 00:22:00 -0000 [thread overview]
Message-ID: <0da09eee-b54e-0232-edb4-41fa805ae473@redhat.com> (raw)
In-Reply-To: <CAFq4t4jSX=2tb0TU61sF4aCUpNyJ26OPK7V0rvVqoLHo4MRWKQ@mail.gmail.com>
On 11/28/2018 10:42 PM, Peter Balazovic wrote:
> this is mine config available on gdb
>
> (gdb) show configuration
> This GDB was configured as follows:
> configure --host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32
^^^^^^^^^^^^^^^^^^^^^^^^^^^
As suspected, here's the problem ^^
> ("Relocatable" means the directory can be moved with the GDB installation
> tree, and GDB will still find it.)
> (gdb) set architecture
> auto i386:intel i386:x64-32 i386:x64-32:nacl
> i386:x86-64:intel i8086
> i386 i386:nacl i386:x64-32:intel i386:x86-64
> i386:x86-64:nacl
As you can see, your build of gdb only supports x86 machines.
With an --enable-targets=all build, I see many, many more entries:
(gdb) set architecture
Requires an argument. Valid arguments are ARC600, A6, ARC601, ARC700, A7, ARCv2, EM, HS, arm, armv2, armv2a, armv3, armv3m, armv4, armv4t, armv5, armv5t, armv5te, xscale, ep9312, iwmmxt, iwmmxt2, armv5tej, armv6, armv6kz, armv6t2, armv6k, armv7, armv6-m, armv6s-m, armv7e-m, armv8-a, armv8-r, armv8-m.base, armv8-m.main, arm_any, avr, avr:1, avr:2, avr:25, avr:3, avr:31, avr:35, avr:4, avr:5, avr:51, avr:6, avr:100, avr:101, avr:102, avr:103, avr:104, avr:105, avr:106, avr:107, bfin, cris, crisv32, cris:common_v10_v32, csky, [...]
ia64-elf64, ia64-elf32, auto.
(gdb)
... including the aarch64 you need:
(gdb) set architecture aarch64<TAB>
aarch64 aarch64:ilp32
>
>
> On Wed, Nov 28, 2018 at 11:28 PM Pedro Alves <palves@redhat.com> wrote:
>
>> On 11/28/2018 06:31 PM, Peter Balazovic wrote:
>>
>>> I am looking for an advice to correctly debug with ARM remote target.
>>
>> Does "set architecture <TAB><TAB>" give you the option to select aarch64?
>>
>> It sounds like your gdb is not configured to support Aarch64.
>>
>> You'll need a gdb configured with
>> --target=aarch64-linux-gnu
>> or
>> --enable-targets=aarch64-linux-gnu
>> --enable-targets=all
>>
>> Try "show configuration" in gdb.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-11-29 0:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 18:31 Peter Balazovic
2018-11-28 18:42 ` Peter Balazovic
2018-11-28 22:28 ` Pedro Alves
2018-11-28 22:42 ` Peter Balazovic
2018-11-29 0:22 ` Pedro Alves [this message]
2018-11-29 6:05 ` Peter Balazovic
2018-11-29 9:52 ` Peter Balazovic
2018-11-29 14:11 ` Pedro Alves
2018-11-28 22:47 ` Peter Balazovic
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=0da09eee-b54e-0232-edb4-41fa805ae473@redhat.com \
--to=palves@redhat.com \
--cc=balazovic.peter@gmail.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