From: Jiri Smid <smid@suse.cz>
To: gdb@sources.redhat.com
Subject: multiarch x86_64 target
Date: Wed, 29 Aug 2001 04:26:00 -0000 [thread overview]
Message-ID: <s8vbskzf6pa.fsf@naga.suse.cz> (raw)
Hello,
I am converting x86_64 target to multiarch as you wanted. The bfd
architecture for both i386 and x86_64 is bfd_arch_i386. And these
targets are diferentiated by machine type.
Due to the i386 target is not yet multiarched I have a problem how to register
x86_64 in gdb.
I have created function i386_gdbarch_init which behaves that if target
vector for machine type differs from bfd_mach_x86_64 should be created
then internal_error(Not yet implemented) is invoked.
But when the gdb starts up then there is created target vector for default
machine type - bfd_mach_i386_i386. Thus gdb can't run.
Do you have any ideas how to solve it?
--
Jiri Smid
---------------------------------------------------------------------
SuSE CR, s.r.o. e-mail: smid@suse.cz
Drahobejlova 27 tel:+420 2 83095 373
190 00 Praha 9 fax:+420 2 83095 374
Ceska republika http://www.suse.cz
next reply other threads:[~2001-08-29 4:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-29 4:26 Jiri Smid [this message]
2001-08-29 8:04 ` Andrew Cagney
2001-08-30 0:05 ` help about debugging embedded linux by GDB target remote debugging agan
2001-09-01 2:34 ` multiarch x86_64 target Mark Kettenis
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=s8vbskzf6pa.fsf@naga.suse.cz \
--to=smid@suse.cz \
--cc=gdb@sources.redhat.com \
/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