[lttng-dev] Weird assertion failure in __lttng_events_init__provider () at /usr/include/lttng/ust-tracepoint-event.h:687
Mathieu Desnoyers
mathieu.desnoyers at efficios.com
Tue Jun 18 09:47:08 EDT 2013
* Amit Margalit (AMITM at il.ibm.com) wrote:
> Hi,
>
> I'm getting an assertion failure as listed above. Any idea what this is?
>
> Program terminated with signal 6, Aborted.
> #0 0x00007fc304edb945 in raise () from /lib64/libc.so.6
> (gdb) bt
> #0 0x00007fc304edb945 in raise () from /lib64/libc.so.6
> #1 0x00007fc304edcf21 in abort () from /lib64/libc.so.6
> #2 0x00007fc304ed4810 in __assert_fail () from /lib64/libc.so.6
> #3 0x00007fc30a48d58a in __lttng_events_init__provider () at
> /usr/include/lttng/ust-tracepoint-event.h:687
>
> The change I made was to add 2 more tracepoints, in a separate file. The
> provider is the same.
It looks like you have duplicated provider objects in your application.
E.g. twice the same provider name trying to register.
Thanks,
Mathieu
>
> I am using --buffers-uid, btw. The code is stock 2.2.0rc2 + my LTTNG_HOME
> patch.
>
> Thanks,
>
>
> Amit Margalit
> IBM XIV - Storage Reinvented
> XIV-NAS Development Team
> Tel. 03-689-7774
> Fax. 03-689-7230
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
More information about the lttng-dev
mailing list