MirOS Manual: addr2line(1)

ADDR2LINE(1)          GNU Development Tools          ADDR2LINE(1)


     addr2line - convert addresses into file names and line


     addr2line [-b bfdname|--target=bfdname]
               [-e filename|--exe=filename]
               [-f|--functions] [-s|--basename]
               [-H|--help] [-V|--version]
               [addr addr ...]


     addr2line translates program addresses into file names and
     line numbers.  Given an address and an executable, it uses
     the debugging information in the executable to figure out
     which file name and line number are associated with a given

     The executable to use is specified with the -e option.  The
     default is the file a.out.

     addr2line has two modes of operation.

     In the first, hexadecimal addresses are specified on the
     command line, and addr2line displays the file name and line
     number for each address.

     In the second, addr2line reads hexadecimal addresses 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

     The format of the output is FILENAME:LINENO.  The file name
     and line number for each address is printed on a separate
     line.  If the -f option is used, then each FILENAME:LINENO
     line is preceded by a FUNCTIONNAME line which is the name of
     the function containing the address.

     If the file name or function name can not be determined,
     addr2line will print two question marks in their place.  If
     the line number can not be determined, addr2line will print


     The long and short forms of options, shown here as
     alternatives, are equivalent.

     -b bfdname

binutils-050707            2015-10-24                           1

ADDR2LINE(1)          GNU Development Tools          ADDR2LINE(1)

         Specify that the object-code format for the object files
         is bfdname.

         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
         Specify the name of the executable for which addresses
         should be translated.  The default file is a.out.

         Display function names as well as file and line number

         Display only the base of each file name.

         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


     Info entries for binutils.


     Copyright (c) 1991, 1992, 1993, 1994, 1995, 1996, 1997,
     1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005 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.1 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''.

binutils-050707            2015-10-24                           2

Generated on 2015-10-25 00:47:46 by $MirOS: src/scripts/roff2htm,v 1.81 2015/10/16 13:19:09 tg Exp $

These manual pages and other documentation are copyrighted by their respective writers; their source is available at our CVSweb, AnonCVS, and other mirrors. The rest is Copyright © 2002–2015 The MirOS Project, Germany.
This product includes material provided by mirabilos.

This manual page’s HTML representation is supposed to be valid XHTML/1.1; if not, please send a bug report – diffs preferred.