The Linux Manuals (man pages) document is an important part of Linux documents. Linux Manuals are organized as several sections. Each section has a group of commands for a specific area in Linux usage, administration or development.
abrt-action-list-dsos – Prints out DSO from mapped memory regions. Synopsisabrt-action-list-dsos [-o OUTFILE] -m PROC_PID_MAP_FILE DescriptionThe tool reads a file containing the mapped memory regions. Output is printed to stdout or file. Output format: %p %n %v %i where %p path to library or binary file, which is mapped in memory region %n name, version, release,…
abrt-action-install-debuginfo – Install debuginfos for build-ids Synopsisabrt-action-install-debuginfo [-vy] [–ids=BUILD_IDS_FILE] [–tmpdir=TMPDIR] [–cache=CACHEDIR[:DEBUGINFODIR1:DEBUGINFODIR2…]] [–size_mb=SIZE] [-e PATH] DescriptionInstalls debuginfos for all build-ids listed in BUILD_IDS_FILE to CACHEDIR, using TMPDIR as temporary staging area. Old files in CACHEDIR are deleted until it is smaller than SIZE. Options-v Be more verbose. Can be given multiple times. -y Noninteractive, assume Yes…
abrt-action-generate-core-backtrace – Generates coredump-level backtrace Synopsisabrt-action-generate-core-backtrace [-v] [-r] [-d DIR] DescriptionThis tool uses coredump from the file coredump and binary at the path stored in file executable in the problem directory to generate coredump-level backtrace. Coredump-level backtrace resembles ordinary backtrace in that it contains information about call frames present on the stack at the time…
abrt-action-generate-backtrace – Analyzes coredump, generates and saves backtrace. Synopsisabrt-action-generate-backtrace [-v] [-d DIR] [-i DIR1[:DIR2]…] [-t NUM] DescriptionThis tool runs gdb(1) on a file named coredump in problem directory DIR. gdb(1) generates backtrace and other diagnostic information about the state of the application at the moment when coredump was generated. Then the tool saves it as…
abrt-action-analyze-xorg – Calculate and save UUID and duplicate hash for a problem data directory DIR with Xorg backtrace. Synopsisabrt-action-analyze-xorg [-v] [-d DIR] DescriptionThe tool reads the file named Xorg.0.log and checks if any black listed module was loaded. If so, not-reportable file is created with an appropriate explanation text. If no black listed module was…
abrt-action-analyze-vulnerability – Provides assessment of potential exploitability of crash Synopsisabrt-action-analyze-vulnerability DescriptionThis tool expects that file named coredump is placed in the current directory and runs abrt-gdb-exploitable gdb plugin on that file. The result of vulnerability analysis is saved in exploitable file in the current directory. This tool requires both gdb and eu-readelf executables placed in…
abrt-action-analyze-vmcore – Extracts the oops message from the kernel core and install the kernel debuginfo if needed Synopsisabrt-action-analyze-vmcore [-v] [-d PROBLEM_DIR] [–tmpdir=TMPDIR] [–cache=DIR1[:DIR2]] DescriptionThe tool reads the file named vmcore from a problem data directory, processes it and the oops message from it. Then it saves this data as new element backtrace. Integration with ABRT…
abrt-action-analyze-python – Calculate and save UUID and duplicate hash for a problem data directory DIR with Python crash data. Synopsisabrt-action-analyze-python [-v] [-d DIR] DescriptionThe tool reads the file named backtrace from a problem data directory, parses it as a Python exception and generates a duplication hash and a universally unique identifier (UUID). Then it saves…
abrt-action-analyze-oops – Calculate and save UUID and duplicate hash for a problem data directory DIR with kernel oops. Synopsisabrt-action-analyze-oops [-v] [-d DIR] DescriptionThe tool reads the file named backtrace from a problem data directory, parses it as a kernel oops record and generates a duplication hash and a universally unique identifier (UUID). Then it saves…
abrt-action-analyze-java – Calculate and save UUID & DUPHASH and determine the level of usability for reporting of a Java stack trace. Synopsisabrt-action-analyze-java [-v] [-d DIR] [-o] [-f FILE] DescriptionThe tool reads the file named backtrace from a problem data directory, processes it and generates a universally unique identifier (UUID). Then it saves this data as…
abrt-action-analyze-core – Extracts builds from a core dump Synopsisabrt-action-analyze-core [-v] [-o OUTFILE] -c COREFILE DescriptionThe tool reads a core dump and extracts build ids of loaded modules and prints the list to the standard output if the OUTFILE file is not configured. Options-c COREFILE Path to a core dump. -v Be more verbose. Can be…
abrt-action-analyze-ccpp-local – Generates backtrace and search for duplicates Synopsisabrt-action-analyze-ccpp-local [–without-di][–without-bz][–without-bodhi] DescriptionThis tool downloads debuginfo and generates a backtrace for coredump in the problem directory, also checks for existing duplicates in bugzilla and possible updates related to the detected crash Integration with ABRT eventsabrt-action-analyze-ccpp-local is used in the analyze step when processing C/C++ crashes EVENT=analyze_LocalGDB analyzer=CCpp…
abrt-action-analyze-c – Calculate and save UUID for a problem data directory DIR with coredump. Synopsisabrt-action-analyze-c [-v] [-d DIR] DescriptionThe tool reads the file named coredump from a problem data directory, processes it and generates a universally unique identifier (UUID). Then it saves this data as new element uuid. Integration with ABRT eventsabrt-action-analyze-c can be used…
abrt-action-analyze-backtrace – Analyzes C/C++ backtrace, generates duplication hash, backtrace rating, and identifies crash function in problem directory DIR. Synopsisabrt-action-analyze-backtrace [-v] [-d DIR] DescriptionThe tool reads a file named backtrace from problem directory, generates duplication hash, backtrace rating, and identifies crash function. Then it saves this data as new elements duphash, rating, crash_function in this problem…
abook – text-based address book program Synopsisabook [ OPTION ] DescriptionThis manual page documents briefly the abook program. This manual page was written for the Debian GNU/Linux distribution because the original program does not have a manual page. abook is a text-based address book program. It contains Name, Email, Address and various Phone fields. It…
abiword — flexible cross-platform word processor Synopsisabiword [OPTIONS] [FILENAME…] DescriptionAbiWord is a full-featured, efficient word processing application suitable for a wide range of word processing tasks, and extensible with a variety of plugins. It integrates with enchant(1) to provide spell-checking. Options-g WxH[+X+Y], –geometry=WxH[+X+Y] Specifies window geometry at startup. -E PLUGIN, –plugin=PLUGIN Execute the specified plugin…
abipkgdiff – compare ABIs of ELF files in software packages abipkgdiff compares the Application Binary Interfaces (ABI) of the ELF binaries contained in two software packages. The software package formats currently supported are Deb, RPM, tar archives (either compressed or not) and plain directories that contain binaries. For a comprehensive ABI change report that includes…
abilint – validate an abigail ABI representation abilint parses the native XML representation of an ABI as emitted by abidw. Once it has parsed the XML representation of the ABI, abilint builds and in-memory model from it. It then tries to save it back to an XML form, to standard output. If that read-write operation…
abidw – serialize the ABI of an ELF file abidw reads a shared library in ELF format and emits an XML representation of its ABI to standard output. The emitted representation includes all the globally defined functions and variables, along with a complete representation of their types. It also includes a representation of the globally…
abidiff – compare ABIs of ELF files abidiff compares the Application Binary Interfaces (ABI) of two shared libraries in ELF format. It emits a meaningful report describing the differences between the two ABIs. For a comprehensive ABI change report that includes changes about function and variable sub-types, the two input shared libraries must be accompanied…