blocks|key|2897661|text|对于“二进制文件”、“图像文件”或“对象文件”，没有严格的定义。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2897662|特别是，“对象文件”一词有时可能被用来指编译器输出的中间文件，以供链接器使用，但在另一上下文中，可能是指可执行文件。|2897663|特别是在不同的平台上，它们可能被用来指不同或相似的事物。即使在一个平台上讨论问题时，一个作者使用的术语也可能与另一个不同。|2897664|至于"PE“和"COFF"，我记得微软使用"COFF”规范作为"PE“规范的起点，但根据他们的需要进行了扩展。严格地说，"PE“文件不是"COFF”文件，但在许多方面非常相似。|2897665|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

There are no strict definitions for the terms 'binary file', 'image file', or 'object file'.

Particularly the term 'object file' might sometimes be used to mean an intermediate file output by the compiler for use by the linker, but in another context might mean an executable file.

Especially on different platforms they might be used for refer to different or similar things. Even when discussing issues on a single platform, one writer might use the terms somewhat differently than another.

As far as "PE" vs "COFF", my recollection is that Microsoft use the "COFF" specification as the starting point for the "PE" specification but extended it for their needs. So strictly speaking a "PE" file isn't a "COFF" file, but it's very similar in many ways.

blocks|key|1217783|text|gcc+-c将在Linux系统上生成一个.o文件，这是一个精灵格式的对象文件。"ELF+32位LSB可重定位，Intel+80386，version+1+(SYSV)“是如何用文件命令在我的机器上描述.o文件的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1217784|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

gcc -c will produce a .o file, which is an elf format object file, on a Linux system. "ELF 32-bit LSB relocatable, Intel 80386, version 1 (SYSV)" is how a .o file is described by the file command on my machine.

blocks|key|1373705|text|对于ELF的Q2，ELF不仅是图像文件的格式，也是对象文件的格式。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1373706|每个ELF文件都以一个精灵头开头。ELF头的第二个字段是e_type；这个字段让我们知道该文件是一个对象文件(在ELF术语中是可重定位的)、图像(可以是可执行的或共享的对象)还是其他的东西(核心文件的也是ELF文件)。|CODE|1373707|entityMap|0|LINK|mutability|MUTABLE|url|http://www.sco.com/developers/gabi/1998-04-29/ch4.eheader.html^0|N|2|0|S|6|B|3|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@$9|U|A|V|B|H]]|D|@$9|W|A|X|1|Y]]|E|$]]|$1|I|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|J|$K|$5|L|M|N|E|$O|P]]]]

In regards to Q2 for ELF, ELF is not only the format of the image file but is also the format of the object file.

Every ELF file starts with an <a href="http://www.sco.com/developers/gabi/1998-04-29/ch4.eheader.html" rel="nofollow noreferrer">ELF Header</a>. The second field of an ELF Header is <code>e_type</code>; this fields lets us know whether the file is an object file (aka a relocatable in ELF parlance), an image (which can be either an executable or a shared object) or something else (core file's are also ELF files).

blocks|key|1373769|text|我是行动组。每个人的答案都是部分答案。所以，我把所有其他的答案和我学到的东西结合起来，来完成这个答案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1373770|这是“通用”使用的术语。|offset|length|style|BOLD|1373771|作为链接器输入的文件(汇编程序的输出)称为Object+File或Relocatable+File。|unordered-list-item|CODE|1373772|链接器生成一个Image+file，然后加载程序将其用作输入。现在，Image+file既可以是Executable+file，也可以是Library+file。这些“图书馆文件”有两种：|1373773|1.+Static+Library+(\*.lib+files+for+windows.+\*.a+for+linux)+
2.+Shared/Dynamic+libraries+:+`DLL`+(+\*.dll+on+windows)+&+`Shared+Object+file`(+\*.so+in+Linux)|code-block|syntax|javascript|1373774|​|1373775|术语Binary+File+/+Binary可以用来指ObjectFile或ImageFile。取决于上下文。这是一个非常笼统的术语。|1373776|当将图像文件加载到内存中时加载程序。然后它被称为Module+(我不确定Linux的家伙，但是windows的人称之为Module|1373777|http://www.gliffy.com/pubdoc/1978433/L.jpg+alt文本http://www.gliffy.com/pubdoc/1978433/L.jpg|1373778|正如我所说的，这些都是“--通常是”使用的术语。对于“二进制文件”、“图像文件”或“对象文件”，没有严格的定义。|1373779|特别是，“对象文件”一词有时可能被用来指编译器输出的中间文件，以供链接器使用，但在另一上下文中，可能是指可执行文件。|1373780|特别是在不同的平台上，它们可能被用来指不同或相似的事物。即使在一个平台上讨论问题时，一个作者使用的术语也可能与另一个不同。|1373781|在linux中，ObjectFile和ImageFile都是PE格式的windows和ELF格式。|1373782|ELF不仅是图像文件的格式，也是对象文件的格式。|1373783|每个ELF文件都以ELF头开头。ELF头的第二个字段是e_type；这个字段让我们知道该文件是一个对象文件(在ELF术语中是可重定位的)，还是一个图像(可以是一个可执行文件，也可以是一个共享对象)，或者其他什么东西(核心文件也是ELF文件)。|1373784|我不知道头中是否有任何一点可以区分对象文件和图像文件。需要检查一下。|1373785|我知道PE是从COFF衍生出来的。但是为什么微软的PE格式规范被命名为“和公共对象文件格式规范”。他们还支持COFF吗？如果他们，在哪个操作系统？我以为PE很久以前就完全取代了COFF了。|blockquote|1373786|至于"PE“和"COFF"，我记得微软使用"COFF”规范作为"PE“规范的起点，但根据他们的需要进行了扩展。严格地说，"PE“文件不是"COFF”文件，但在许多方面非常相似。|1373787|entityMap|0|LINK|mutability|MUTABLE|url|http://www.gliffy.com/pubdoc/1978433/L.jpg|1^0|0|3|2|0|L|B|X|G|0|7|A|Y|A|1C|F|1W|C|0|0|0|2|B|G|6|0|O|6|1N|6|0|0|16|0|17|1B|1|0|C|5|0|0|0|0|0|R|6|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1T|8|@$D|1U|E|1V|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|1W|8|@$D|1X|E|1Y|F|K]|$D|1Z|E|20|F|K]]|9|@]|A|$]]|$1|L|3|M|5|J|7|21|8|@$D|22|E|23|F|K]|$D|24|E|25|F|K]|$D|26|E|27|F|K]|$D|28|E|29|F|K]]|9|@]|A|$]]|$1|N|3|O|5|P|7|2A|8|@]|9|@]|A|$Q|R]]|$1|S|3|T|5|6|7|2B|8|@]|9|@]|A|$]]|$1|U|3|V|5|J|7|2C|8|@$D|2D|E|2E|F|K]|$D|2F|E|2G|F|K]]|9|@]|A|$]]|$1|W|3|X|5|J|7|2H|8|@$D|2I|E|2J|F|K]|$D|2K|E|2L|F|K]]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|2M|8|@]|9|@$D|2N|E|2O|1|2P]|$D|2Q|E|2R|1|2S]]|A|$]]|$1|10|3|11|5|6|7|2T|8|@$D|2U|E|2V|F|G]]|9|@]|A|$]]|$1|12|3|13|5|6|7|2W|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|2X|8|@]|9|@]|A|$]]|$1|16|3|17|5|J|7|2Y|8|@]|9|@]|A|$]]|$1|18|3|19|5|J|7|2Z|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|J|7|30|8|@$D|31|E|32|F|K]]|9|@]|A|$]]|$1|1C|3|1D|5|J|7|33|8|@]|9|@]|A|$]]|$1|1E|3|1F|5|1G|7|34|8|@]|9|@]|A|$]]|$1|1H|3|1I|5|6|7|35|8|@]|9|@]|A|$]]|$1|1J|3|-4|5|6|7|36|8|@]|9|@]|A|$]]]|1K|$1L|$5|1M|1N|1O|A|$1P|1Q]]|1R|$5|1M|1N|1O|A|$1P|1Q]]]]

I'm the OP. Every one's answer is a partial answer. So, I'm combining all the other answers with what I learnt to complete the answer.

This is the "Generally" used terminology.

<ul>
<li>A file that is given as input to the linker (output of assembler) is called <code>Object File</code> or <code>Relocatable File</code>. </li>
<li>The linker produces an <code>Image file</code>, which in turn is used as input by the loader. Now, an <code>Image file</code> can either be an <code>Executable file</code> or <code>Library file</code>. These 'Library files' are of two kinds: 

<ol>
<li>Static Library (*.lib files for windows. *.a for linux) </li>
<li>Shared/Dynamic libraries : <code>DLL</code> ( *.dll on windows) &amp; <code>Shared Object file</code>( *.so in Linux)</li>
</ol></li>
<li>The term <code>Binary File</code> / <code>Binary</code> can be used to refer to either an ObjectFile or an ImageFile. Undestand depending up on the context. It is a very general term.</li>
<li>Loader when loads the image file into memory. Then it is called <code>Module</code> (I'm not sure about Linux guys, but windows guys call it <code>Module</code></li>
</ul>

<a href="http://www.gliffy.com/pubdoc/1978433/L.jpg" rel="noreferrer">http://www.gliffy.com/pubdoc/1978433/L.jpg</a>
<a href="http://www.gliffy.com/pubdoc/1978433/L.jpg" rel="noreferrer">alt text http://www.gliffy.com/pubdoc/1978433/L.jpg</a>

As I said, these are "Generally" used terminology. There are no strict definitions for the terms 'binary file', 'image file', or 'object file'.

Particularly the term 'object file' might sometimes be used to mean an intermediate file output by the compiler for use by the linker, but in another context might mean an executable file.

Especially on different platforms they might be used for refer to different or similar things. Even when discussing issues on a single platform, one writer might use the terms somewhat differently than another.

<ul>
<li>Both ObjectFile &amp; ImageFile are in PE Format in windows &amp; ELF format in linux.</li>
<li>ELF is not only the format of the image file but is also the format of the object file.</li>
<li>Every ELF file starts with an ELF Header. The second field of an ELF Header is <code>e_type</code>; this fields lets us know whether the file is an object file (aka a relocatable in ELF parlance), or an image (which can be either an executable or a shared object) or something else (core file's are also ELF files).</li>
<li>I don't know if there is any bit in header that differentiates an Object file from Image file. It needs to be checked.</li>
</ul>

<blockquote>
 I know that PE is derived from COFF.
 But why does the Microsoft
 specifications of PE format is named
 Microsoft Portable Executable "and
 Common Object File Format
 Specification". Do they still support
 COFF? If they, in which OS? I thought
 PE completely replaced COFF long ago.
</blockquote>

As far as "PE" vs "COFF", my recollection is that Microsoft use the "COFF" specification as the starting point for the "PE" specification but extended it for their needs. So strictly speaking a "PE" file isn't a "COFF" file, but it's very similar in many ways.

blocks|key|1217820|text|顺便提一下，我知道Solaris上的核心转储(我猜还有其他Unix版本)可以采用ELF格式。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1217821|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

As an aside, I know core dumps on Solaris (and I am guessing other Unix flavors) can be in ELF format.

I'm confusing little in terminology.
<blockquote>
A file that is given as input to the linker is called Object File.
The linker produces an Image file, which in turn is used as input by the loader.
</blockquote>
I got this from &quot;MS PE &amp; COFF Specification&quot;
Q1. Image file is also referred to as <code>Binary Image</code>, <code>Binary File</code> or just <code>Binary</code>. Right?
Q2. So, according to the above stated terminology, the PE/ELF/COFF are the formats of Image File &amp; not the Object File. right? But <a href="http://www.sco.com/developers/gabi/latest/ch4.intro.html" rel="noreferrer">http://www.sco.com/developers/gabi/latest/ch4.intro.html</a> says
<blockquote>
This chapter describes the object file format, called ELF (Executable and Linking Format). There are three main types of object files.
<ul>
<li>A relocatable file holds code and data suitable for linking with other
object files to create an executable
or a shared object file.
</li>
<li>An executable file holds a program suitable for execution; the
file specifies how exec(BA_OS) creates
a program's process image.
</li>
<li>A shared object file holds code and data suitable for linking in two
contexts. First, the link editor [see
ld(BA_OS)] processes the shared object
file with other relocatable and shared
object files to create another object
file. Second, the dynamic linker
combines it with an executable file
and other shared objects to create a
process image.
</li>
</ul>
</blockquote>
contradictorily he is saying that both Object File &amp; Image File are ELF formats &amp; He is not at all differentiating between object &amp; image files but referring them commonly as Object files. Isn't it wrong?
Q3. I know that PE is derived from COFF. But why does the Microsoft specifications of PE format is named Microsoft Portable Executable &quot;and Common Object File Format Specification&quot;. Do they still support COFF? If they, in which OS? I thought PE completely replaced COFF long ago.

Clarification on Binary file (PE/COFF & ELF) formats & terminology

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我在术语上一点也不困惑。作为链接器输入的文件称为对象文件。链接器生成一个图像文件，然后加载程序使用该文件作为输入。我是从"MS PE & COFF规范“得到的Q1.图像文件也称为Binary Image、Binary File或仅为Binary。对吗？因此，根据上述术语，PE/ELF/COFF是图像文件的格式，而不是对...

问对二进制文件(PE/COFF & ELF)格式和术语的澄清
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问对二进制文件(PE/COFF & ELF)格式和术语的澄清EN