From: Michal Ludvig <mludvig@suse.cz>
To: gdb@sources.redhat.com
Subject: Adding dwarf2 regnum mapping
Date: Mon, 29 Apr 2002 10:58:00 -0000 [thread overview]
Message-ID: <3CCD899D.3020903@suse.cz> (raw)
Hi,
I'm adding x86_64_dwarf2_reg_to_regno() function but don't know how to
let gdb know it's there. I got inspired by i386 and put
#define DWARF2_REG_TO_REGNUM(reg) x86_64_dwarf2_reg_to_regnum ((reg))
into nm-x86-64.h. Unfortunately then the compilation fails with:
gdbarch.h:664:2: #error "Non multi-arch definition of DWARF2_REG_TO_REGNUM"
If I don't put this define into nm.h, the new function isn't used at
all. Can someone please tell me how do I tell gdb about this function
while retaining the target multiarch_pure? If I change the target to
multiarch_partial, everything works just fine, but I don't think it's
the right way to go.
Thanks in advance.
Michal Ludvig
--
* SuSE CR, s.r.o * mludvig@suse.cz
* +420 2 9654 5373 * http://www.suse.cz
next reply other threads:[~2002-04-29 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 10:58 Michal Ludvig [this message]
2002-04-29 11:44 ` Daniel Jacobowitz
2002-04-30 3:01 ` Michal Ludvig
2002-04-29 12:18 ` Jim Blandy
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=3CCD899D.3020903@suse.cz \
--to=mludvig@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