From: Ian Lance Taylor <ian@zembu.com>
To: bcombee@metrowerks.com
Cc: binutils@sourceware.cygnus.com
Subject: Re: DWARF info on i386-ELF Linux -- need pointers
Date: Thu, 01 Jul 1999 00:00:00 -0000 [thread overview]
Message-ID: <19990623021342.25208.qmail@daffy.airs.com> (raw)
In-Reply-To: <041601bebd02$3f7c5650$3404010a@metrowerks.com>
From: "Ben Combee" <bcombee@metrowerks.com>
Date: Tue, 22 Jun 1999 17:54:56 -0500
I'm trying to produce DWARF debugging information suitable for use with gdb
and the binutils on i386 ELF-based Linux. I've read the DWARF 1.1
specification and looked at the source code for BFD, but I cannot figure out
the right mapping of x86 registers to DWARF register numbers. Can anyone
here provide me a pointer as to where to look? I'm especially interested in
the floating point/MMX registers, as EAX-EBP have fairly obvious encodings
based on the opcode format.
There are two natural places to look: gcc and gdb. gcc has to
generate the register mappings, and gdb has to interpret them. The
binutils don't care.
In gcc, see DBX_REGISTER_NUMBER in gcc/config/i386/sysv4.h.
In gdb, I think the right place is gdb/config/i386/tm-i386.h.
However, I believe that in neither place will you find any register
number assignments for the MMX registers. I don't think gcc ever
generates code that uses the MMX registers, so it does not need to
define any debugging information for them.
Ian
prev parent reply other threads:[~1999-07-01 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 0:00 adding c4x port to binutils distribution Greg Smart
1999-07-01 0:00 ` DWARF info on i386-ELF Linux -- need pointers Ben Combee
1999-07-01 0:00 ` Jeffrey A Law
1999-07-01 0:00 ` Ian Lance Taylor [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=19990623021342.25208.qmail@daffy.airs.com \
--to=ian@zembu.com \
--cc=bcombee@metrowerks.com \
--cc=binutils@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).