a.out

From Wikipedia, the free encyclopedia

Please help improve this article or section by expanding it.
Further information might be found on the talk page or at requests for expansion. (January 2007)

a.out
File name extension	`none, .o, .so`
Developed by	AT&T
Type of format	Binary, executable, object, shared libraries

a.out is a file format used in older versions of Unix-like computer operating systems for executables, object code, and, in later systems, shared libraries. The name stands for assembler output.

a.out remains the default output file name for executables created by certain compilers/linkers when no output name was specified, even though these executables were no longer in the a.out format.^[1]

1 Use
2 Format
3 References
4 External links

[edit] Use

An a.out format for the PDP-7, similar to the a.out format used on the PDP-11, appeared in the first edition of UNIX.^[2] It was superseded by the COFF format in AT&T Unix System V, which was in turn superseded by ELF in System V Release 4.

Though Berkeley Unix kept using a.out for some time, modern BSD-systems have since switched to ELF. NetBSD/i386 switched formally from a.out to ELF in its 1.5 release. FreeBSD/i386 switched to ELF during the 2.2 to 3.0 transition.

The a.out format has no direct support for debug information, but can be used with stabs, which uses special symbol table entries to store data.

Linux also used a.out until kernel 1.2 (ELF support was added in the experimental 1.1.52), when it was superseded by ELF for that platform as well.^[3] Linux's transition to ELF was more or less forced due to the complex nature of building a.out shared libraries on that platform, which included the need to register the virtual address space at which the library was located with a central authority, as the a.out ld.so in Linux was unable to relocate shared libraries.^[4] The various BSD flavours were able to continue using a.out binaries long after Linux was forced to switch to ELF, due to the somewhat more flexible nature of the BSD a.out format compared to that of Linux.^[5]

[edit] Format

a.out executables typically came in one of several variants, OMAGIC, NMAGIC, QMAGIC, or ZMAGIC. The OMAGIC format had contiguous segments after the header, with no separation of text and data. The NMAGIC format was similar to OMAGIC, however the data segment was loaded on the immediate next page after the end of the text segment, and the text segment was marked read-only. The ZMAGIC format added support for demand paging, and QMAGIC allowed the a.out header to be merged with the first page of the text segment, typically saving a page worth of memory. QMAGIC binaries were typically loaded one page above the bottom of the virtual address space, in order to permit trapping of null pointer dereferences via a segmentation fault.

An a.out file consists of up to 7 sections. In order, these sections are:

exec header: Contains parameters used by the kernel to load a binary file into memory and execute it, and by the link editor ld to combine a binary file with other binary files. This section is the only mandatory one.
text segment: Contains machine code and related data that are loaded into memory when a program executes. May be loaded read-only.
data segment: Contains initialized data; always loaded into writable memory.
text relocations: Contains records used by the link editor to update pointers in the text segment when combining binary files.
data relocations: Like the text relocation section, but for data segment pointers.
symbol table: Contains records used by the link editor to cross-reference the addresses of named variables and functions (symbols) between binary files.
string table: Contains the character strings corresponding to the symbol names.