DEMANGLE(1) [FIXME: manual] DEMANGLE(1)NAME
demangle - Undo C++ name mangling for symbols
SYNOPSIS
demangle
DESCRIPTION
demangle reads a list of C++ mangled symbol names from standard input and converts these names to human-readable form on standard output.
This utility is part of the KDE Software Development Kit.
EXAMPLE
Create a file called names containing the following mangled symbol names:
_ZNK6Object10metaObjectEv
_ZN8QPtrListI5ArrowE5clearEv
_ZTC4Kolf0_11KMainWindow
These names can then be demangled as follows:
example$ demangle < names
Object::metaObject() const
QPtrList<Arrow>::clear()
construction vtable for KMainWindow-in-Kolf
SEE ALSO kminspector(1)kmtrace(1)match(1)AUTHOR
Ben Burton <bab@debian.org>
Author.
[FIXME: source] April 7, 2003 DEMANGLE(1)
Check Out this Related Man Page
FIXINCLUDES(1) [FIXME: manual] FIXINCLUDES(1)NAME
fixincludes - Reduce the number of #includes in KDE source files
SYNOPSIS
fixincludes [-v, --verbose] [-e, --experimental] [-m, --modify] [file] [--help]
DESCRIPTION
fixincludes tries to reduce the number of #includes in C++ source files. Much of it's processing is specific to KDE sources and so it might
not work so well with sources for non-KDE applications.
The following problems are identified by fixincludes:
o Including headers that are no longer supported but which exist for compatibility with older Qt/KDE versions;
o Including the same file multiple times.
There is also an experimental mode which tries removing each #include one at a time (with a few exceptions) to see whether the source still
compiles. Note that this experimental mode will modify the original sources.
By default the sources will not be modified; the identified problems will simply be written to standard output.
The list of C++ sources to examine should be given on the command-line. If no files are given, all C++ sources in or beneath the current
directory will be examined (with the exception of directories whose Makefile.am contains -UQT_NO_COMPAT or -UKDE_NO_COMPAT)
This utility is part of the KDE Software Development Kit.
OPTIONS -v, --verbose
Verbose mode. Additional debugging output is written to standard output.
-e, --experimental
Experimental mode, as described above in detail. Note that this option implies --modify.
-m, --modify
As well as writing messages to standard output, actually modify the original sources to fix any problems that were found.
AUTHORS
fixincludes was written by Dirk Mueller <mueller@kde.org>.
AUTHOR
Ben Burton <bab@debian.org>
Author.
[FIXME: source] April 7, 2003 FIXINCLUDES(1)
Hello,
i am try to write a profiler for a multithreaded applciation. When i creat e a thread for "function f2()" the profiling information for this function does not get captured in the struct profileManager. i;e i get the exit information for "function f2()" in that thread, but the entry... (2 Replies)
We are moving from old solaris to new version of solaris. I have copied the gcc compiler installed on old server to new solaris server. But just copying didn't work. So I am trying to build it on the new server. The server version is
sailfish@st-kvar02 -> uname -a
SunOS st-kvar02 5.10... (7 Replies)
Hi,
I want to install the gcc-3.4.6 on solaris 9.5 , in order to compile perl 5.8.8 . I have the following packages .
gcc-3.4.6.tar
ibiconv-1.11-sol9-sparc-local.gz
gcc-3.4.6-sol9-sparc-local
libiconv-1.11.tar.gz
Where can I find the necessary documents or... (4 Replies)
Hi ,
I am installing gcc 3.4.6 on SunOS labcvs001sm 5.9 Generic_117171-07 sun4u sparc
SUNW,Ultra-5_10 . The isa info is 'sparcv'.
I have the following with me
a)gcc-3.4.6.tar
b)gcc-3.4.6-sol9-sparc-local
c)libiconv-1.11-sol9-sparc-local
d) binutils-2.18.tar.gz
e)... (8 Replies)
Hello. I used to compile my code including a third-party library, "libfoo.so". Now, the vendor ships a statically linked library, "libfoo.a", instead. With this library, I run into the following error:
CC -mt -xarch=v9 -DCOMPILE_SOL_SPARC -ftrap=%none -xlibmil -xchip=ultra2 -xbuiltin -xO4 \... (0 Replies)
Hi Gurus,
I need to check whether the compiler installed in my system supports 64bit compilation.
Server - Sun fire v490
OS - Solaris 5.9
Processor - Sparcv9 (64bit)
Install Directory - /opt/SUNWSpro
Compiler Model - Sun Forte C Compiler.
My development team is claiming that there... (20 Replies)
Hello. I'm using SunStudio 12 Update 1. When compiling for x86, everything works fine. When compiling for SPARC, I get the following errors. I linked libCstd.so.1 explicitly, but I get the same errors. Would anyone be kind enough to step me through resolving this? Thank you very much.
**... (2 Replies)
Hello All,
i am porting my application from SunSolaris to Linux (RHEL4).
When i compile my c/c++ code i am getting the following errors.
1. catastrophic error: could not open source file "sys/elf_386.h"
#include <sys/elf_386.h>
2. catastrophic error: could not open source file... (2 Replies)