lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: RADERMACHER Ansgar via lttng-dev <lttng-dev@lists.lttng.org>
To: Philippe Proulx <eeppeliteloop@gmail.com>
Cc: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] [barectf] How to ensure that last events before a crash get recorded
Date: Fri, 5 Mar 2021 12:27:53 +0000	[thread overview]
Message-ID: <386C5D4D5C53C24CBC2C60CAAFD2136A5B4B2E34@EXDAG0-B1.intra.cea.fr> (raw)
In-Reply-To: <CAB4xu_38oAbOD606ZQCp71oJ8qwYOt7F1Ssmpk=idhhTM7to6w@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2007 bytes --]

Hi Philippe,

thanks for your response. The reason not to use LTTng is simple: while I develop on Linux, our client is chiefly using Windows with the mingw environment.

Best regards

Ansgar

________________________________
From: P
hilippe Proulx [eeppeliteloop@gmail.com]
Sent: Friday, March 05, 2021 13:11
To: RADERMACHER Ansgar
Cc: lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] [barectf] How to ensure that last events before a crash get recorded

On Thu, Mar 4, 2021 at 10:28 RADERMACHER Ansgar via lttng-dev <lttng-dev@lists.lttng.org<mailto:lttng-dev@lists.lttng.org>> wrote:
Hi,

when doing tracing with barectf, the trace elements are written into a buffer first and only written when the buffer is full - or if the function barectf_platform_fs_fini gets called.
In case of a crash, it's therefore possible to loose some events. What is the best option to prevent this issue? I've used signal handlers that call the function barectf_platform_fs_fini. This seems to work well with Linux, but is not portable. When using the provided sample platform, there is also the option to reduce the buffer size, but this is not ideal, as trace events that are too big for the buffer are not written.

First question: why are you using barectf on Linux vs LTTng?

LTTng supports writing the sub-buffers to NVRAM and, if the system crashes, convert those sub-buffers to a CTF trace with the lttng-crash utility. See <
https://lttng.org/docs/v2.12/#doc-persistent-memory-file-systems>.

With NVRAM, you could do this with barectf with a corresponding platform using it. It's always up to the platform author to decide where buffers are and where complete packets go; it's not a feature of barectf as such.

Hope it helps,

Phil


Best regards

Ansgar


_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org<mailto:lttng-dev@lists.lttng.org>
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
--
Philippe Proulx

[-- Attachment #1.2: Type: text/html, Size: 4594 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

      reply	other threads:[~2021-03-05 13:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04 15:06 RADERMACHER Ansgar via lttng-dev
2021-03-05 12:11 ` Philippe Proulx via lttng-dev
2021-03-05 12:27   ` RADERMACHER Ansgar via lttng-dev [this message]

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=386C5D4D5C53C24CBC2C60CAAFD2136A5B4B2E34@EXDAG0-B1.intra.cea.fr \
    --to=lttng-dev@lists.lttng.org \
    --cc=Ansgar.RADERMACHER@cea.fr \
    --cc=eeppeliteloop@gmail.com \
    --subject='Re: [lttng-dev] [barectf] How to ensure that last events before a crash get recorded' \
    /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

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).