ADDR2LINE(1)

📦
version 2.47+3build2 · 7 versions
, in ubuntu stonking

💖 ADDR2LINE(1) 💖

so bestie, this is the addr2line page from the GNU Development Tools manual, and honestly? it's giving translator-girlie energy. it takes your cryptic little addresses and turns them into actual real-world locations in your code. periodt.

✨ NAME ✨

addr2line — convert addresses or symbol+offset into file names and line numbers

🎀 SYNOPSIS 🎀

addr2line [-a|--addresses]
          [-b bfdname|--target=bfdname]
          [-C|--demangle[=style]]
          [-r|--no-recurse-limit]
          [-R|--recurse-limit]
          [-e filename|--exe=filename]
          [-f|--functions] [-s|--basename]
          [-i|--inlines]
          [-p|--pretty-print]
          [-j|--section=name]
          [-H|--help] [-V|--version]
          [addr addr ...]

🌈 DESCRIPTION 🌈

okay so here's the vibe: addr2line translates addresses or symbol+offset into file names and line numbers. you hand it an address or symbol+offset inside an executable, or an offset inside a section of a relocatable object, and it goes digging through the debugging information to figure out which file name and line number are associated with it. it's literally the glow-up your hex dumps have been waiting for. 💅

the executable or relocatable object you want it to peek at is specified with the -e option. the default is the file a.out (yes, just sitting there being the default like it owns the place). the section in the relocatable object to use is specified with the -j option.

addr2line has two modes of operation, and yes both are iconic in their own way:

  1. in the first mode, hexadecimal addresses or symbol+offset are specified on the command line, and addr2line displays the file name and line number for each address.
  2. in the second mode, addr2line reads hexadecimal addresses or symbol+offset from standard input, and prints the file name and line number for each address on standard output. in this mode, addr2line may be used in a pipe to convert dynamically chosen addresses. pipe girlies rise up 🫶

the format of the output is FILENAME:LINENO. by default each input address generates one line of output.

so there are two options that can generate additional lines before each FILENAME:LINENO line — and they show up in that order, no queue-jumping:

  • if the -a option is used, then a line with the input address is displayed.
  • if the -f option is used, then a line with the FUNCTIONNAME is displayed. this is the name of the function containing the address.

and there's one option that can generate additional lines after the FILENAME:LINENO line:

  • if the -i option is used and the code at the given address is present there because of inlining by the compiler, then additional lines are displayed afterwards. one or two extra lines (if the -f option is used) are displayed for each inlined function.

alternatively, if the -p option is used, then each input address generates a single, long, output line containing the address, the function name, the file name and the line number. if the -i option has also been used then any inlined functions will be displayed in the same manner, but on separate lines, and prefixed by the text (inlined by). lowkey a whole mood board of information in one line.

if the file name or function name can not be determined, addr2line will print two question marks in their place (??, the shrug emoji of debug info 😭). if the line number can not be determined, addr2line will print 0.

when symbol+offset is used, +offset is optional, except when the symbol is ambigious with a hex number. the resolved symbols can be mangled or unmangled, except unmangled symbols with + are not allowed. (yes, "ambigious" is spelled exactly like that in here. we don't fix, we report. 💀)

💅 OPTIONS 💅

the long and short forms of options, shown here as alternatives, are equivalent. choose your fighter.

  • -a, --addresses — display the address before the function name, file and line number information. the address is printed with a 0x prefix to easily identify it.
  • -b bfdname, --target=bfdname — specify that the object-code format for the object files is bfdname.
  • -C, --demangle[=style] — decode (demangle) low-level symbol names into user-level names. besides removing any initial underscore prepended by the system, this makes C++ function names readable. different compilers have different mangling styles. the optional demangling style argument can be used to choose an appropriate demangling style for your compiler.
  • -e filename, --exe=filename — specify the name of the executable for which addresses should be translated. the default file is a.out.
  • -f, --functions — display function names as well as file and line number information.
  • -s, --basenames — display only the base of each file name.
  • -i, --inlines — if the address belongs to a function that was inlined, the source information for all enclosing scopes back to the first non-inlined function will also be printed. for example, if "main" inlines "callee1" which inlines "callee2", and address is from "callee2", the source information for "callee1" and "main" will also be printed. nesting dolls but make it source code 🪆
  • -j, --section — read offsets relative to the specified section instead of absolute addresses.
  • -p, --pretty-print — make the output more human friendly: each location are printed on one line. if option -i is specified, lines for all enclosing scopes are prefixed with (inlined by).
  • -r, -R, --recurse-limit, --no-recurse-limit, --recursion-limit, --no-recursion-limit — enables or disables a limit on the amount of recursion performed whilst demangling strings. since the name mangling formats allow for an infinite level of recursion it is possible to create strings whose decoding will exhaust the amount of stack space available on the host machine, triggering a memory fault. the limit tries to prevent this from happening by restricting recursion to 2048 levels of nesting.

the default is for this limit to be enabled, but disabling it may be necessary in order to demangle truly complicated names.

⚠️ note however that if the recursion limit is disabled then stack exhaustion is possible and any bug reports about such an event will be rejected. read that again, bestie. rejected. 🙈

the -r option is a synonym for the --no-recurse-limit option. the -R option is a synonym for the --recurse-limit option.

note this option is only effective if the -C or --demangle option has been enabled. so it does nothing on its own, it needs its demangle bestie present. 🫶

  • @file — read command-line options from file. the options read are inserted in place of the original @file option. if file does not exist, or cannot be read, then the option will be treated literally, and not removed.

options in file are separated by whitespace. a whitespace character may be included in an option by surrounding the entire option in either single or double quotes. any character (including a backslash) may be included by prefixing the character to be included with a backslash. the file may itself contain additional @file options; any such options will be processed recursively. it's giving inception, but for flags. 🌸

🦋 SEE ALSO 🦋

  • Info entries for binutils.

Copyright (c) 1991-2026 Free Software Foundation, Inc.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. a copy of the license is included in the section entitled "GNU Free Documentation License".

and that's the whole page, bestie — no notes, ate and left zero crumbs. this was documented by the fine folks at binutils-2.47, dated 2026-09-19, and it is literally the ADDR2LINE(1) era. go translate some addresses, you main character. 💖✨

📦 where this page comes from