Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: russell_klein@mentor.com (Klein, Russell)
Subject: [ltt-dev] Assertion failure
Date: Tue, 30 Nov 2010 11:15:38 -0800	[thread overview]
Message-ID: <0B313B6FF2091F4197B830CF774530F2015ADEBA@na3-mail.mgc.mentorg.com> (raw)
Message-ID: <20101130191538.MBUU6YNZCMgLTBVZZkmZx3vUSH8vJypNEt2fgJnImhM@z> (raw)

I am trying to collect some user space traces using ust version 0.6, and
I am getting the following assertion failure after it runs for a while:

 

<app-name>:  buffers.h:525: ust_buffers_write: Assertion `buf_offset +
len < buf->chan->subbuf_cnt' failed.

Aborted

 

Any ideas on what might be the cause of this or how to avoid it?

 

Thanks, Russ Klein

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20101130/339e79b0/attachment-0002.htm>


             reply	other threads:[~2010-11-30 19:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30 19:15 Klein, Russell [this message]
2010-11-30 19:15 ` Klein, Russell
2010-11-30 19:15 ` Klein, Russell
2010-11-30 19:30 ` Mathieu Desnoyers
2010-11-30 19:33   ` Klein, Russell
2010-11-30 20:25     ` Mathieu Desnoyers

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=0B313B6FF2091F4197B830CF774530F2015ADEBA@na3-mail.mgc.mentorg.com \
    --to=russell_klein@mentor.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