Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [ltt-dev] Assert error ust strncpy
Date: Tue, 17 Aug 2010 18:21:28 -0400	[thread overview]
Message-ID: <20100817222128.GA4641@Krystal> (raw)
In-Reply-To: <4C6B075C.3090207@polymtl.ca>

* David Goulet (david.goulet at polymtl.ca) wrote:
> Hi Mathieu,
>
> I have a quite big problem since the new patch with strncpy for UST.
>
> With a high number of events (100000 +), I got this :
>
> buffers.h:525: ust_buffers_write: Assertion `buf_offset + len <  
> buf->chan->subbuf_size*buf->chan->subbuf_cnt' failed.
>
> At that line in (libust/buffers.h) you have two asserts and the first  
> one seems not needed because the second assert check the exact same  
> thing with "len" added... but still apply for the case of the first one.

If the first fails, then we know the the value fails, then then second, we know
it's len that makes it fail. It's not useless.

I found the problem. Off by one in my assert. Will post a patch in a jiffy.

Thanks,

Mathieu

>
> Anyway, is this means that the subbuffers are full? I'm actually in  
> OVERWRITE mode so... why does the tracing stop there?
>
> Test case (tar.gz) in attachment. Tested on 2 separate machines.
>
> UST_TRACE=1 UST_AUTOPROBE=1 UST_OVERWRITE=1 UST_AUTOCOLLECT=0  
> ./withtracepoint 1 10000000
>
> Thanks
> -- 
> David Goulet
> LTTng project, DORSAL Lab.
>
> PGP/GPG : 1024D/16BD8563
> BE3C 672B 9331 9796 291A  14C6 4AF7 C14B 16BD 8563



-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com




      parent reply	other threads:[~2010-08-17 22:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-17 22:04 David Goulet
2010-08-17 22:04 ` David Goulet
2010-08-17 22:04 ` David Goulet
2010-08-17 22:21 ` Mathieu Desnoyers [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=20100817222128.GA4641@Krystal \
    --to=mathieu.desnoyers@efficios.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