[lttng-dev] [PATCH lttng-tool] Fix: mi: Make sure GIT_VERSION symbol always exist

The use of GIT_VERSION symbol in mi to express the position in git tree force the need to have it defined for each type of build. This make sure that a build from source file only (git scm not present) is possible. Signed-off-by: Jonathan Rajotte Julien --- include/Makefile.am| 15 ++--

[lttng-dev] [PATCH lttng-tools] Add the formal version before the git version for a commit outside the master branch

Signed-off-by: Raphaël Beamonte --- include/Makefile.am | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/include/Makefile.am b/include/Makefile.am index d40cb4a..67a7063 100644 --- a/include/Makefile.am +++ b/include/Makefile.am @@ -24,8 +24,10 @@ version.h:

[lttng-dev] [PATCH lttng-tool] Fix: mi: logically dead code, missing ret assignment

Signed-off-by: Jonathan Rajotte Julien --- src/bin/lttng/commands/list.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/bin/lttng/commands/list.c b/src/bin/lttng/commands/list.c index 210c2f4..956b62e 100644 --- a/src/bin/lttng/commands/list.c +++ b/src/bin/lttng/commands

[lttng-dev] [PATCH lttng-tool] Always print GIT_VERSION even if empty

Adjustment from last proposed patch. Less crowded and more standard. This should not break any packaging. feedback? Signed-off-by: Jonathan Rajotte Julien --- include/Makefile.am | 14 +- include/version.h.tmpl | 9 + src/bin/lttng/commands/version.c

Re: [lttng-dev] [PATCH lttng-tools] Change wfq usages for wfcq

As agreed on #lttng, I've merged that patch and changed the requirements for userspace RCU from >= 0.7.2 to >= 0.8.0. Thanks! David On 28 Jul (15:10:44), Simon Marchi wrote: > On 28 July 2014 14:50, David Goulet wrote: > > So there is quite an issue with that which is that tools does not work >

Re: [lttng-dev] [PATCH lttng-tools] Change wfq usages for wfcq

On 28 July 2014 14:50, David Goulet wrote: > So there is quite an issue with that which is that tools does not work > with urcu 0.7 anymore. > > That would mean urcu 0.8 and later would be the requirement from now on. Ok, so the version number of urcu in configure.ac should be updated too. > Not

Re: [lttng-dev] [PATCH lttng-tools] Change wfq usages for wfcq

So there is quite an issue with that which is that tools does not work with urcu 0.7 anymore. That would mean urcu 0.8 and later would be the requirement from now on. Not sure I'm comfortable with that but again I don't see why we should not do that also David On 26 Jul (01:26:56), Simon Ma

Re: [lttng-dev] User Space Events Not creating Logs

Is this reproductible on stable 2.5? Thanks, Jérémie On Mon, Jul 28, 2014 at 1:36 AM, RGIAS MUG wrote: > Hi All, > > I am using the lttng (LTTng Trace Control) 2.3.1 - Dominus Vobiscum. > I had attached the log file with lttng-sessiond and sample user space > tracing applivcation with fu

Re: [lttng-dev] [PATCH lttng-tools] Fix: unbalanced ustconsumer32_data.pid_mutex lock

Merged and backported! Thanks! David On 27 Jul (20:38:50), Mathieu Desnoyers wrote: > It is never locked in this function, but should be. This is triggering > spurious runtime failures on my system, where it seems that sessiond was > sometimes breaking the communication pipe with liblttng-ctl whe

Re: [lttng-dev] Duplicate registration of tracepoint probes

I figured it out. The duplicate __tracepoint__init_urcu_sym symbols apparently aren't an issue. The problem is that I had tracepoints in a static library that was then linked into the main executable as well as a dynamic library loaded by the executable. (It wasn't obvious because the relevant s

[lttng-dev] User Space Events Not creating Logs

Hi All, I am using the lttng (LTTng Trace Control) 2.3.1 - Dominus Vobiscum. I had attached the log file with lttng-sessiond and sample user space tracing applivcation with full verbosity option. The User space tracing events logs were not available. Same thing when i tried in ubu