lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: Umut Tezduyar Lindskog <umut@tezduyar.com>
To: Venkata Kantimahanthi <venkata.kantimahanthi@tcs.com>
Cc: lttng-dev@lists.lttng.org
Subject: Re: Path for core dump
Date: Thu, 19 Feb 2015 08:49:56 +0100	[thread overview]
Message-ID: <CAFKnvs5O7h4P-3TB+m4b64jV96SuZVPnFZ8CyvS+GLuUPQZexg__5525.36701220578$1424332309$gmane$org@mail.gmail.com> (raw)
In-Reply-To: <OFB56050E8.48E7632E-ON65257DF1.00192C9D-65257DF1.0019B94A@tcs.com>

Hi Venkata,

Coredumps are passed to the program that is specified with
/proc/sys/kernel/core_pattern. Depending on what program is defined,
you should retrieve the dump from there.

For example, if you had systemd, coredumps are passed to
systemd-coredump program and they can be viewed/retrieved with
coredumpctl.

Umut

On Thu, Feb 19, 2015 at 5:39 AM, Venkata Kantimahanthi
<venkata.kantimahanthi@tcs.com> wrote:
> Hi,
>
>  Once I have seen a crash in babeltrace, does any one know where to find the
> coredump? (I am running  BabelTrace Trace Viewer and Converter 1.2.1)
> babeltrace -i lttng-live net://127.0.0.1/host/du1/testF
> [error] No metadata stream opened
> Segmentation fault (core dumped)
>
>
> Thanks & Regards
> Venkata Ranganadh Kantimahanthi
> Tata Consultancy Services
> Cell:- +919494595225
> Mailto: venkata.kantimahanthi@tcs.com
> Website: http://www.tcs.com
> ____________________________________________
> Experience certainty.        IT Services
>                        Business Solutions
>                        Consulting
> ____________________________________________
>
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>

       reply	other threads:[~2015-02-19  7:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OFB56050E8.48E7632E-ON65257DF1.00192C9D-65257DF1.0019B94A@tcs.com>
2015-02-19  7:49 ` Umut Tezduyar Lindskog [this message]
2015-02-19  4:39 Path for core dump Venkata Kantimahanthi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFKnvs5O7h4P-3TB+m4b64jV96SuZVPnFZ8CyvS+GLuUPQZexg__5525.36701220578$1424332309$gmane$org@mail.gmail.com' \
    --to=umut@tezduyar.com \
    --cc=lttng-dev@lists.lttng.org \
    --cc=venkata.kantimahanthi@tcs.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).