2012-10-19 14:29:46 +04:00
<?xml version='1.0'?> <!-- * - nxml - * -->
< !DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
2015-06-18 20:47:44 +03:00
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
2012-10-19 14:29:46 +04:00
<!--
This file is part of systemd.
Copyright 2012 Zbigniew Jędrzejewski-Szmek
systemd is free software; you can redistribute it and/or modify it
under the terms of the GNU Lesser General Public License as published by
the Free Software Foundation; either version 2.1 of the License, or
(at your option) any later version.
systemd is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public License
along with systemd; If not, see <http: / / w w w . g n u . o r g / l i c e n s e s /> .
-->
2014-06-19 15:46:01 +04:00
<refentry id= "coredumpctl" conditional= 'ENABLE_COREDUMP'
2015-02-04 05:14:13 +03:00
xmlns:xi="http://www.w3.org/2001/XInclude">
<refentryinfo >
<title > coredumpctl</title>
<productname > systemd</productname>
<authorgroup >
<author >
<contrib > Developer</contrib>
<firstname > Zbigniew</firstname>
<surname > Jędrzejewski-Szmek</surname>
<email > zbyszek@in.waw.pl</email>
</author>
</authorgroup>
</refentryinfo>
<refmeta >
<refentrytitle > coredumpctl</refentrytitle>
<manvolnum > 1</manvolnum>
</refmeta>
<refnamediv >
<refname > coredumpctl</refname>
2016-05-16 12:56:04 +03:00
<refpurpose > Retrieve and process saved core dumps and metadata</refpurpose>
2015-02-04 05:14:13 +03:00
</refnamediv>
<refsynopsisdiv >
<cmdsynopsis >
<command > coredumpctl</command>
<arg choice= "opt" rep= "repeat" > OPTIONS</arg>
<arg choice= "req" > COMMAND</arg>
<arg choice= "opt" rep= "repeat" > PID|COMM|EXE|MATCH</arg>
</cmdsynopsis>
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
2016-05-16 12:56:04 +03:00
<para > <command > coredumpctl</command> is a tool that can be used to retrieve and process core
dumps and metadata which were saved by
<citerefentry > <refentrytitle > systemd-coredump</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry> .
</para>
2015-02-04 05:14:13 +03:00
</refsect1>
<refsect1 >
<title > Options</title>
<para > The following options are understood:</para>
<variablelist >
2016-05-16 12:56:04 +03:00
<xi:include href= "standard-options.xml" xpointer= "help" />
<xi:include href= "standard-options.xml" xpointer= "version" />
2015-02-04 05:14:13 +03:00
<varlistentry >
<term > <option > --no-legend</option> </term>
2016-05-16 12:56:04 +03:00
<listitem > <para > Do not print column headers.</para> </listitem>
2015-02-04 05:14:13 +03:00
</varlistentry>
2016-05-16 12:56:04 +03:00
<xi:include href= "standard-options.xml" xpointer= "no-pager" />
2015-02-04 05:14:13 +03:00
<varlistentry >
<term > <option > -1</option> </term>
2016-05-16 12:56:04 +03:00
<listitem > <para > Show information of a single core dump only, instead of listing
all known core dumps.</para> </listitem>
2015-02-04 05:14:13 +03:00
</varlistentry>
<varlistentry >
2015-08-25 21:04:55 +03:00
<term > <option > -F</option> <replaceable > FIELD</replaceable> </term>
<term > <option > --field=</option> <replaceable > FIELD</replaceable> </term>
2015-02-04 05:14:13 +03:00
<listitem > <para > Print all possible data values the specified
2016-05-16 12:56:04 +03:00
field takes in matching core dump entries of the
2015-02-04 05:14:13 +03:00
journal.</para> </listitem>
</varlistentry>
<varlistentry >
2015-08-25 21:04:55 +03:00
<term > <option > -o</option> <replaceable > FILE</replaceable> </term>
<term > <option > --output=</option> <replaceable > FILE</replaceable> </term>
2015-02-04 05:14:13 +03:00
<listitem > <para > Write the core to <option > FILE</option> .
</para> </listitem>
</varlistentry>
2015-08-25 11:36:49 +03:00
<varlistentry >
<term > <option > -D</option> <replaceable > DIR</replaceable> </term>
<term > <option > --directory=</option> <replaceable > DIR</replaceable> </term>
<listitem > <para > Use the journal files in the specified <option > DIR</option> .
</para> </listitem>
</varlistentry>
2015-02-04 05:14:13 +03:00
</variablelist>
2016-05-16 12:56:04 +03:00
</refsect1>
<refsect1 >
<title > Commands</title>
2015-02-04 05:14:13 +03:00
<para > The following commands are understood:</para>
<variablelist >
<varlistentry >
<term > <command > list</command> </term>
2016-05-16 12:56:04 +03:00
<listitem > <para > List core dumps captured in the journal
2015-02-04 05:14:13 +03:00
matching specified characteristics. If no command is
2016-05-16 12:56:04 +03:00
specified, this is the implied default.</para>
<para > It's worth noting that different restrictions apply to
data saved in the journal and core dump files saved in
<filename > /var/lib/systemd/coredump</filename> , see overview in
<citerefentry > <refentrytitle > systemd-coredump</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry> .
Thus it may very well happen that a particular core dump is still listed
in the journal while its corresponding core dump file has already been
removed.</para> </listitem>
2015-02-04 05:14:13 +03:00
</varlistentry>
<varlistentry >
<term > <command > info</command> </term>
2016-05-16 12:56:04 +03:00
<listitem > <para > Show detailed information about core dumps
2015-02-04 05:14:13 +03:00
captured in the journal.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <command > dump</command> </term>
2016-05-16 12:56:04 +03:00
<listitem > <para > Extract the last core dump matching specified
characteristics. The core dump will be written on standard
2015-02-04 05:14:13 +03:00
output, unless an output file is specified with
2015-08-25 21:04:55 +03:00
<option > --output=</option> . </para> </listitem>
2015-02-04 05:14:13 +03:00
</varlistentry>
<varlistentry >
<term > <command > gdb</command> </term>
2016-05-16 12:56:04 +03:00
<listitem > <para > Invoke the GNU debugger on the last core dump
2015-02-04 05:14:13 +03:00
matching specified characteristics. </para> </listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1 >
<title > Matching</title>
<para > A match can be:</para>
<variablelist >
<varlistentry >
<term > <replaceable > PID</replaceable> </term>
<listitem > <para > Process ID of the
process that dumped
core. An integer.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <replaceable > COMM</replaceable> </term>
<listitem > <para > Name of the executable (matches
<option > COREDUMP_COMM=</option> ). Must not contain slashes.
</para> </listitem>
</varlistentry>
<varlistentry >
<term > <replaceable > EXE</replaceable> </term>
<listitem > <para > Path to the executable (matches
<option > COREDUMP_EXE=</option> ). Must contain at least one
slash. </para> </listitem>
</varlistentry>
<varlistentry >
<term > <replaceable > MATCH</replaceable> </term>
<listitem > <para > General journalctl predicates (see
<citerefentry > <refentrytitle > journalctl</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ).
Must contain an equal sign. </para> </listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1 >
<title > Exit status</title>
<para > On success, 0 is returned; otherwise, a non-zero failure
2016-05-16 12:56:04 +03:00
code is returned. Not finding any matching core dumps is treated as
2015-02-04 05:14:13 +03:00
failure.
</para>
</refsect1>
<refsect1 >
<title > Examples</title>
<example >
2016-05-16 12:56:04 +03:00
<title > List all the core dumps of a program named foo</title>
2015-02-04 05:14:13 +03:00
<programlisting > # coredumpctl list foo</programlisting>
</example>
<example >
2016-05-16 12:56:04 +03:00
<title > Invoke gdb on the last core dump</title>
2015-02-04 05:14:13 +03:00
<programlisting > # coredumpctl gdb</programlisting>
</example>
<example >
<title > Show information about a process that dumped core,
matching by its PID 6654</title>
<programlisting > # coredumpctl info 6654</programlisting>
</example>
<example >
2016-05-16 12:56:04 +03:00
<title > Extract the last core dump of /usr/bin/bar to a file named
2015-02-04 05:14:13 +03:00
<filename noindex= "true" > bar.coredump</filename> </title>
<programlisting > # coredumpctl -o bar.coredump dump /usr/bin/bar</programlisting>
</example>
</refsect1>
<refsect1 >
<title > See Also</title>
<para >
<citerefentry > <refentrytitle > systemd-coredump</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > coredump.conf</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd-journald.service</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry> ,
<citerefentry project= 'man-pages' > <refentrytitle > gdb</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry>
</para>
</refsect1>
2012-10-19 14:29:46 +04:00
</refentry>