This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: MIPS MS ECOFF file format

From: Ian Lance Taylor <ian at wasabisystems dot com>
To: "Alexander Voropay" <alec at artcoms dot ru>
Cc: "Eric Christopher" <echristo at redhat dot com>, <binutils at sources dot redhat dot com>
Date: 03 Dec 2004 08:59:33 -0500
Subject: Re: MIPS MS ECOFF file format
References: <005601c4d89b$9a1ed960$6cf9a8c0@ALEC><1102015965.3416.8.camel@localhost.localdomain><m33byotrtp.fsf@gossamer.airs.com><001501c4d92c$b9df63f0$6cf9a8c0@ALEC>

"Alexander Voropay" <alec@artcoms.ru> writes:

>  No, as it is known, the PE files has a MS-DOS "MZ" header, but this
> file looks like bare COFF/ECOFF/XCOFF MS's variant.

Are you sure that is true of non-i386 COFF/PE files?

Note that there is no standard MIPS COFF.  MIPS ECOFF files look like
COFF files at the start, so when BFD sees a MIPS COFF file, it tries
to interpret it as ECOFF.  The symbol table and relocation entries are
different in COFF and ECOFF.

>  Is there any tool to dump an ECOFF file content precisely ? (not `objbump`)

Look at mips-tdump in the gcc distribution.  It doesn't print all
information, but it does print the ECOFF symbol table and
mdebug-format debugging information.

Ian

Follow-Ups:
- Re: MIPS MS ECOFF file format
  - From: Alexander Voropay

References:
- MIPS MS ECOFF file format
  - From: Alexander Voropay
- Re: MIPS MS ECOFF file format
  - From: Eric Christopher
- Re: MIPS MS ECOFF file format
  - From: Ian Lance Taylor
- Re: MIPS MS ECOFF file format
  - From: Alexander Voropay

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]