View source for DWARF

{{short description|Standardized debugging data format}}
{{other uses|Dwarf (disambiguation)}}
{{primary sources|date=July 2017}}
'''DWARF''' is a widely used, standardized [[debugging data format]]. DWARF was originally designed along with [[Executable and Linkable Format]] (ELF), although it is independent of [[object file]] formats.<ref name=eager>{{cite web | url = https://dwarfstd.org/doc/Debugging%20using%20DWARF-2012.pdf | title = Introduction to the DWARF Debugging Format | accessdate = 2015-01-08 | author = Michael J. Eager | date = April 2012 }}</ref> The name is a [[medieval fantasy]] complement to "ELF" that had no official meaning, although the name "Debugging With Arbitrary Record Formats" has since been proposed as a [[backronym]].<ref name=eager/>
DWARF originated with the C compiler and sdb debugger in [[Unix System V]] Release 4 (SVR4).<ref name=eager/>
== History ==
The first version of DWARF proved to use excessive amounts of storage, and an incompatible successor, DWARF-2, superseded it and added various encoding schemes to reduce data size. DWARF did not immediately gain universal acceptance; for instance, when [[Sun Microsystems]] adopted ELF as part of their move to [[Solaris (operating system)|Solaris]], they opted to continue using [[stabs]], in an embedding known as "stabs-in-elf". [[Linux]] followed suit, and DWARF-2 did not become the default until the late 1990s.
The DWARF Workgroup of the [[Free Standards Group]] released DWARF version 3 in January 2006,<ref>{{cite press release | publisher = Free Standards Group | title = DWARF Version 3 Standard Released | date = January 4, 2006 | accessdate = 2007-06-25 | url = http://dwarfstd.org/PressRelease.php | archive-date = 2011-07-25 | archive-url = https://web.archive.org/web/20110725074306/http://dwarfstd.org/PressRelease.php | url-status = dead }}</ref> adding (among other things) support for [[C++]] namespaces, [[Fortran#Fortran 90|Fortran 90]] {{mono|allocatable}} data and additional [[compiler optimization]] techniques.
The DWARF committee published version 4 of DWARF, which offers "improved data compression, better description of optimized code, and support for new language features in C++", in 2010.<ref>{{cite web |url=http://dwarfstd.org/Announcement.php |title=DWARF Version 4 Released |publisher=The DWARF committee |date=June 16, 2010 |accessdate=2010-06-24 |archive-date=2020-07-30 |archive-url=https://web.archive.org/web/20200730064541/http://dwarfstd.org/Announcement.php |url-status=dead }}</ref>
Version 5 of the DWARF format was published in February 2017.<ref>{{cite web |url=http://dwarfstd.org/DWARF5PressRelease.php |title=DWARF Version 5 Standard Released |publisher=The DWARF committee |date= February 15, 2017 |accessdate = 2017-08-07 }}</ref><ref>{{cite web |url=http://dwarfstd.org/Dwarf5Std.php |title=DWARF 5 Standard |publisher=The DWARF committee |date= February 15, 2017  |accessdate = 2017-08-07}}</ref> It "incorporates improvements in many areas: better data compression, separation of debugging data from executable files, improved description of macros and source files, faster searching for symbols, improved debugging of optimized code, as well as numerous improvements in functionality and performance."
== Structure ==
DWARF uses a data structure called a Debugging Information Entry (DIE) to represent each variable, type, procedure, etc. A DIE has a tag (e.g., {{mono|DW_TAG_variable}}, {{mono|DW_TAG_pointer_type}}, {{mono|DW_TAG_subprogram}}) and attributes (key-value pairs). A DIE can have nested (child) DIEs, forming a [[tree (data structure)|tree]] structure. A DIE attribute can refer to another DIE anywhere in the tree—for instance, a DIE representing a variable would have a {{mono|DW_AT_type}} entry pointing to the DIE describing the variable's type.
To save space, two large tables needed by symbolic debuggers are represented as [[Bytecode|byte-coded]] instructions for simple, special-purpose [[finite state machine]]s. The Line Number Table, which maps code locations to source code locations and vice versa, also specifies which instructions are part of [[function prologue]]s and epilogues. The Call Frame Information table allows debuggers to locate frames on the [[call stack]].
DWARF has been divided into different sections like [[.debug_info]],<ref>[https://developer.ibm.com/articles/au-dwarf-debug-format/ .debug_info ibm documenation]</ref> .debug_frame, etc.
== Tools ==
Libdwarf is a library that provides access to the DWARF debugging information in executable files and object files.<ref>{{Cite web |title=libdwarf: A Consumer Library Interface to DWARF |url=https://www.prevanders.net/libdwarfdoc/ |access-date=2023-12-06 |website=www.prevanders.net}}</ref>
== Further reading ==
Michael Eager, chair of the DWARF Standards Committee, has written an introduction to debugging formats and DWARF 3, ''Introduction to the DWARF Debugging Format''.<ref name=eager/>
== References ==
{{refs}}
== External links ==
* {{official website|http://dwarfstd.org/}}
* [http://www.prevanders.net/dwarf.html Libdwarf], a C library intended to simplify reading (and writing) applications using DWARF2, DWARF3.
* [http://sourceware.org/elfutils elfutils], [[GNU_Binutils#elfutils|another C library]] for ELF/DWARF file processing.
* [http://eli.thegreenplace.net/2011/02/07/how-debuggers-work-part-3-debugging-information/ How debuggers work]: Part 3 - Debugging information
* [https://web.archive.org/web/20180808115504/http://www.ibm.com/developerworks/library/os-debugging/ Debugging formats DWARF and STAB]
[[Category:Debugging data formats]]