Scroll to navigation

LLVM-SYMBOLIZER(1) LLVM LLVM-SYMBOLIZER(1)

NAME

llvm-symbolizer - convert addresses into source code locations

SYNOPSIS

llvm-symbolizer [options]

DESCRIPTION

llvm-symbolizer reads object file names and addresses from standard input and prints corresponding source code locations to standard output. If object file is specified in command line, llvm-symbolizer reads only addresses from standard input. This program uses debug info sections and symbol table in the object files.

EXAMPLE

$ cat addr.txt
a.out 0x4004f4
/tmp/b.out 0x400528
/tmp/c.so 0x710
/tmp/mach_universal_binary:i386 0x1f84
/tmp/mach_universal_binary:x86_64 0x100000f24
$ llvm-symbolizer < addr.txt
main
/tmp/a.cc:4


f(int, int)
/tmp/b.cc:11


h_inlined_into_g
/tmp/header.h:2
g_inlined_into_f
/tmp/header.h:7
f_inlined_into_main
/tmp/source.cc:3
main
/tmp/source.cc:8


_main
/tmp/source_i386.cc:8


_main
/tmp/source_x86_64.cc:8
$ cat addr2.txt
0x4004f4
0x401000
$ llvm-symbolizer -obj=a.out < addr2.txt
main
/tmp/a.cc:4


foo(int)
/tmp/a.cc:12


OPTIONS

-obj
Path to object file to be symbolized.

-functions=[none|short|linkage]
Specify the way function names are printed (omit function name, print short function name, or print full linkage name, respectively). Defaults to linkage.

-use-symbol-table
Prefer function names stored in symbol table to function names in debug info sections. Defaults to true.

-demangle
Print demangled function names. Defaults to true.

-inlining
If a source code location is in an inlined function, prints all the inlnied frames. Defaults to true.

-default-arch
If a binary contains object files for multiple architectures (e.g. it is a Mach-O universal binary), symbolize the object file for a given architecture. You can also specify architecture by writing binary_name:arch_name in the input (see example above). If architecture is not specified in either way, address will not be symbolized. Defaults to empty string.

EXIT STATUS

llvm-symbolizer returns 0. Other exit codes imply internal program error.

AUTHOR

Maintained by The LLVM Team (http://llvm.org/).

COPYRIGHT

2003-2014, LLVM Project
2015-02-27 3.5