From: Daniel Jacobowitz <drow@false.org>
To: shrimpx@gmail.com
Cc: gdb@sourceware.org
Subject: Re: trying to understand some BFD code
Date: Tue, 02 Oct 2007 22:39:00 -0000 [thread overview]
Message-ID: <20071002223914.GA14646@caradoc.them.org> (raw)
In-Reply-To: <f72a771a0710021531m67607b08mc84361bf4a4ee25c@mail.gmail.com>
On Tue, Oct 02, 2007 at 03:31:10PM -0700, shrimpx@gmail.com wrote:
> Hi all,
>
> I've asked a similar question before, but I'm still trying to
> understand some stuff in how BFD works, for a research project I'm
> working on. Help would be much appreciated!
BFD comes from binutils, not from GDB. Also, roughly no one works
with a.out any more, so you're unlikely to find much help. Sorry.
> Could someone explain why this is the case?
>
> Is it fundamentally tied to the endianness of binary formats? If so,
> why are the *bits* inside r_type[0] reversed? To my knowledge,
> bfd_header_big_endian() indicates the byte-endianness of the format.
I would assume that it is a peculiarity of the a.out format, not
anything more general.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-10-02 22:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 22:31 shrimpx
2007-10-02 22:39 ` Daniel Jacobowitz [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=20071002223914.GA14646@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=shrimpx@gmail.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