From mboxrd@z Thu Jan 1 00:00:00 1970 From: david.goulet@polymtl.ca (David Goulet) Date: Tue, 17 Aug 2010 18:04:12 -0400 Subject: [ltt-dev] Assert error ust strncpy Message-ID: <4C6B075C.3090207@polymtl.ca> 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. 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: ust-error-test.donut Type: application/octet-stream Size: 3365 bytes Desc: not available URL: From mboxrd@z Thu Jan 1 00:00:00 1970 From: david.goulet@polymtl.ca (David Goulet) Date: Tue, 17 Aug 2010 18:04:12 -0400 Subject: [ltt-dev] Assert error ust strncpy Message-ID: <4C6B075C.3090207@polymtl.ca> Message-ID: <20100817220412.zI47FQGTqKPmoVoWKqPiXb4jncdG3iX4YIFSec15kVw@z> 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. 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: ust-error-test.donut Type: application/octet-stream Size: 3365 bytes Desc: not available URL: From mboxrd@z Thu Jan 1 00:00:00 1970 From: david.goulet@polymtl.ca (David Goulet) Date: Tue, 17 Aug 2010 18:04:12 -0400 Subject: [ltt-dev] Assert error ust strncpy Message-ID: <4C6B075C.3090207@polymtl.ca> Message-ID: <20100817220412.6m4G-hpi8gM_04CARQ5YERzdYZa0EDFB31m_dP7fbg4@z> 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. 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: ust-error-test.donut Type: application/octet-stream Size: 3365 bytes Desc: not available URL: