From: Kevin Buettner <kevinb@redhat.com>
To: <vincent.girard-reydet@bull.net>
Cc: <gdb@sources.redhat.com>
Subject: Re: ia64 in-target debugging
Date: Tue, 06 Apr 2004 15:50:00 -0000 [thread overview]
Message-ID: <20040406085032.0106df53@saguaro> (raw)
In-Reply-To: <PMECLFNHMJECAIEDIAAPMECLCAAA.vincent.girard-reydet@bull.net>
On Tue, 6 Apr 2004 14:18:36 +0200
"Vincent Girard-Reydet" <vincent.girard-reydet@bull.net> wrote:
> I'm writing a stub for gdb on ia64 machines in order to debug a BIOS (in
> fact it will be a stub for the EFI/ia64). I intend to debug my ia64 server
> from a x86 laptop through a serial line.
> I saw in the archives that it might not be possible to achieve it. Any
> comments about it ? Have you any clues (or pointers to some how-to) on how I
> could compile gdb on my laptop to get this stuff working ? The problem is
> that if I do a ./configure, I think gdb will know x86, but not ia64, and I
> need him to know both of them.
Use configure's --target switch. E.g.
./configure --target=ia64-elf
> I also need some informations about the executable formats supported by GDB.
> The EFI spec requires PE32+ executable format (extension of the PE/COFF
> format), but it's not clear if GDB supports it. If not, any idea of the
> amount of work needed to support it ?
I don't know. Take a look at the bfd directory to see if this support
exists.
> Also, I don't know where to post my stub when it is debugged. If someone
> could tell me, this would be great.
gdb-patches@sources.redhat.com
If you plan on contributing code to GDB, you should make sure that you
have an FSF copyright assignment in order.
Kevin
prev parent reply other threads:[~2004-04-06 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 12:23 Vincent Girard-Reydet
2004-04-06 15:50 ` Kevin Buettner [this message]
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=20040406085032.0106df53@saguaro \
--to=kevinb@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=vincent.girard-reydet@bull.net \
/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