From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13503 invoked by alias); 2 Oct 2007 22:39:20 -0000 Received: (qmail 13493 invoked by uid 22791); 2 Oct 2007 22:39:20 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 02 Oct 2007 22:39:17 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id C60CC98152; Tue, 2 Oct 2007 22:39:15 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 9BB029810B; Tue, 2 Oct 2007 22:39:15 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.67) (envelope-from ) id 1IcqOY-0003qI-R4; Tue, 02 Oct 2007 18:39:14 -0400 Date: Tue, 02 Oct 2007 22:39:00 -0000 From: Daniel Jacobowitz To: shrimpx@gmail.com Cc: gdb@sourceware.org Subject: Re: trying to understand some BFD code Message-ID: <20071002223914.GA14646@caradoc.them.org> Mail-Followup-To: shrimpx@gmail.com, gdb@sourceware.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.15 (2007-04-09) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-10/txt/msg00029.txt.bz2 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