Ok. When trying to instrument a bigger application (memcached) with the same pattern, I witnessed a different behavior. No crash on assert, but only one tracepoint would get correctly registered at the application startup (as I mentionned on IRC this weekend). So the behavior when doing this seems undefined. Maybe this restriction should be documented ? It seemed natural to me at first to put each tracepoint in its own .tp file.
On 29 April 2013 12:25, Mathieu Desnoyers <[email protected]> wrote: > You should not create two compilation units with the same provider name > in your application. This assertion is there to check just that. > > * Simon Marchi ([email protected]) wrote: >> Hello ! >> >> I am trying to add two tracepoints to a simple test application. If I >> put both tracepoints in different compilation units (two .c files), >> UST crashes when the application starts with the following message: >> >> test: /usr/local/include/lttng/ust-tracepoint-event.h:685: >> __lttng_events_init__my_project: Assertion `!ret' failed. >> >> I made an example [1] so you can simply run "make && ./test". I am >> using the latest git versions, on Ubuntu 13.04 x86_64. >> >> Thanks ! >> >> Simon >> >> [1] http://git.dorsal.polymtl.ca/~smarchi?p=ust-test.git;a=summary >> >> _______________________________________________ >> lttng-dev mailing list >> [email protected] >> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev > > -- > Mathieu Desnoyers > EfficiOS Inc. > http://www.efficios.com > > _______________________________________________ > lttng-dev mailing list > [email protected] > http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev _______________________________________________ lttng-dev mailing list [email protected] http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
