c++filt (1)
Leading comments
Automatically generated by Pod::Man 4.09 (Pod::Simple 3.35) Standard preamble: ========================================================================
NAME
c++filt - Demangle C++ and Java symbols.SYNOPSIS
c++filt [-_|--strip-underscore][-n|--no-strip-underscore]
[-p|--no-params]
[-t|--types]
[-i|--no-verbose]
[-s format|--format=format]
[--help] [--version] [symbol...]
DESCRIPTION
The CEvery alphanumeric word (consisting of letters, digits, underscores, dollars, or periods) seen in the input is a potential mangled name. If the name decodes into a C
You can also use c++filt to decipher individual symbols by passing them on the command line:
c++filt <symbol>
If no symbol arguments are given, c++filt reads symbol names from the standard input instead. All the results are printed on the standard output. The difference between reading names from the command line versus reading names from the standard input is that command line arguments are expected to be just mangled names and no checking is performed to separate them from surrounding text. Thus for example:
c++filt -n _Z1fv
will work and demangle the name to ``f()'' whereas:
c++filt -n _Z1fv,
will not work. (Note the extra comma at the end of the mangled name which makes it invalid). This command however will work:
echo _Z1fv, | c++filt -n
and will display ``f(),'', i.e., the demangled name followed by a trailing comma. This behaviour is because when the names are read from the standard input it is expected that they might be part of an assembler source file where there might be extra, extraneous characters trailing after a mangled name. For example:
.type _Z1fv, @function
OPTIONS
- -_
- --strip-underscore
-
On some systems, both the C and C++compilers put an underscore in front of every name. For example, the C name "foo" gets the low-level name "_foo". This option removes the initial underscore. Whether c++filt removes the underscore by default is target dependent.
- -n
- --no-strip-underscore
- Do not remove the initial underscore.
- -p
- --no-params
- When demangling the name of a function, do not display the types of the function's parameters.
- -t
- --types
- Attempt to demangle types as well as function names. This is disabled by default since mangled types are normally only used internally in the compiler, and they can be confused with non-mangled names. For example, a function called ``a'' treated as a mangled type name would be demangled to ``signed char''.
- -i
- --no-verbose
- Do not include implementation details (if any) in the demangled output.
- -s format
- --format=format
-
c++filt can decode various methods of mangling, used by
different compilers. The argument to this option selects which
method it uses:
-
- auto
- Automatic selection based on executable (the default method)
- gnu
-
the one used by the GNU Ccompiler (g++)++
- lucid
- the one used by the Lucid compiler (lcc)
- arm
-
the one specified by the C++Annotated Reference Manual
- hp
-
the one used by the HPcompiler (aCC)
- edg
-
the one used by the EDGcompiler
- gnu-v3
-
the one used by the GNU Ccompiler (g++) with the V3++ABI.
- java
-
the one used by the GNUJava compiler (gcj)
- gnat
-
the one used by the GNUAda compiler (GNAT).
-
- --help
- Print a summary of the options to c++filt and exit.
- --version
- Print the version number of c++filt and exit.
- @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.
FOOTNOTES
- 1.
-
MS-DOS does not allow "+" characters in file names, so on
MS-DOS this program is named CXXFILT.
SEE ALSO
the Info entries for binutils.COPYRIGHT
Copyright (c) 1991-2015 Free Software Foundation, Inc.Permission is granted to copy, distribute and/or modify this document under the terms of the