Alexandre Montplaisir | 22 May 20:36 2015

[lttng-modules PATCH] Fix: Update kmem event for recent Ubuntu kernel

Ubuntu backported a patch into their 3.13 (Trusty) branch which
changes kmem event definition.

Upstream commit
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=99592d598eca62bdbbf62b59941c189176dfc614
first appears in 4.0 (and was later backported to 3.19.2).
We already have the proper check for this.

This corresponds to Ubuntu commit
http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/?id=d938e4bff1089a1f4757ed94a5cace803c6a363b
which was first released with 3.13.0-50.82.
This required adding a new check specifically for the
Ubuntu version.

Signed-off-by: Alexandre Montplaisir <alexmonthy <at> voxpopuli.im>
---
 instrumentation/events/lttng-module/kmem.h | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/instrumentation/events/lttng-module/kmem.h b/instrumentation/events/lttng-module/kmem.h
index ee83d38..1d4eb62 100644
--- a/instrumentation/events/lttng-module/kmem.h
+++ b/instrumentation/events/lttng-module/kmem.h
 <at>  <at>  -202,7 +202,8  <at>  <at>  LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(kmem_mm_page, mm_page_pcpu_drain,

 #if (LINUX_VERSION_CODE >= KERNEL_VERSION(3,19,2)	\
 	|| LTTNG_KERNEL_RANGE(3,14,36, 3,15,0)		\
-	|| LTTNG_DEBIAN_KERNEL_RANGE(3,16,7,9,0,0, 3,17,0,0,0,0))
+	|| LTTNG_DEBIAN_KERNEL_RANGE(3,16,7,9,0,0, 3,17,0,0,0,0)	\
+	|| LTTNG_UBUNTU_KERNEL_RANGE(3,13,0,50, 3,14,0,0))
(Continue reading)

Benjamin Poirier | 21 May 01:32 2015
Picon

[PATCH latency_tracker] Use $(src) rather than pwd to identify the source tree.

This fixes the build when using kernels older than "aa55c8e kbuild: handle
C=... and M=... after entering into build directory (v3.18-rc1)" and a
separate object output directory (`make O=...`).

Signed-off-by: Benjamin Poirier <bpoirier <at> suse.de>
---
 Makefile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Makefile b/Makefile
index 360b24b..de141df 100644
--- a/Makefile
+++ b/Makefile
 <at>  <at>  -1,4 +1,4  <at>  <at> 
-ccflags-y += -I$(PWD)/include $(EXTCFLAGS)
+ccflags-y += -I$(src)/include $(EXTCFLAGS)

 latency_tracker-objs := tracker.o rculfhash.o rculfhash-mm-chunk.o wfcqueue.o

--

-- 
2.3.5
Thomas Bertauld | 20 May 22:31 2015
Picon

LTTng-modules install failed on a Parallella

Hi !

I recently began to work on a Parallella board and I wanted to try tracing the ARM processor with LTTng before doing ant work with the Epiphany chip (co-processor).

Nevertheless, i'm stuck with an error anytime i try to install the lttng-modules. I've tried installing it from the official repositories and from the PPA but none worked.

For now i only tried with the headless version of Ubuntu 14.04 (http://www.parallella.org/create-sdcard/) for the Zynq-7010 (the processor itself is a ARM Cortex A9).

The kernel version is 3.14.12, as seen in the error message below


parallella <at> parallella:~$ sudo apt-get install lttng-modules-dkms
Reading package lists... Done
Building dependency tree      
Reading state information... Done
The following extra packages will be installed:
  dkms
The following NEW packages will be installed:
  dkms lttng-modules-dkms
0 upgraded, 2 newly installed, 0 to remove and 1 not upgraded.
Need to get 286 kB of archives.
After this operation, 2816 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://ports.ubuntu.com/ trusty-updates/main dkms all 2.2.0.3-1.1ubuntu5.14.04 [64.6 kB]
Get:2 http://ports.ubuntu.com/ trusty-updates/universe lttng-modules-dkms all 2.4.0-1ubuntu1.1 [221 kB]
Fetched 286 kB in 0s (356 kB/s)        
Selecting previously unselected package dkms.
(Reading database ... 39070 files and directories currently installed.)
Preparing to unpack .../dkms_2.2.0.3-1.1ubuntu5.14.04_all.deb ...
Unpacking dkms (2.2.0.3-1.1ubuntu5.14.04) ...
Selecting previously unselected package lttng-modules-dkms.
Preparing to unpack .../lttng-modules-dkms_2.4.0-1ubuntu1.1_all.deb ...
Unpacking lttng-modules-dkms (2.4.0-1ubuntu1.1) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Setting up dkms (2.2.0.3-1.1ubuntu5.14.04) ...
Setting up lttng-modules-dkms (2.4.0-1ubuntu1.1) ...
Loading new lttng-modules-2.4.0 DKMS files...
First Installation: checking all kernels...
dpkg: warning: version '*-*' has bad syntax: version number does not start with digit
It is likely that 3.14.12-parallella-xilinx-g40a90c3 belongs to a chroot's host


And at this point the installation just stop and i'm back with the prompt.

Since i'm quite new in the LTTng universe i don't know what to do. I made some researches on the subject but there was nothing for the Parallella. I only found an answer for a similar problem suggesting to install the kernel causing this trouble in the chroot environment, but i'm not quite sure how to do this properly.

Thanks in advance !

Thomas.
_______________________________________________
lttng-dev mailing list
lttng-dev <at> lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
Partha Pratim Mukherjee | 20 May 20:59 2015
Picon

[PATCH lttng-tools] Fix: destroy session removes the default config file

Destroy session command by default removes the default config file
without checking the current session. As a result when we call any
other command which expects a default session by calling
get_session_name() function, it fails.

This patch will fix this by checking that the default config file gets
removed only when destroy session is called with the current session.

Fixes: #887

Signed-off-by: Partha Pratim Mukherjee <ppm.floss <at> gmail.com>
---
 src/bin/lttng/commands/destroy.c |    4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/src/bin/lttng/commands/destroy.c b/src/bin/lttng/commands/destroy.c
index 95343c9..3fcecc2 100644
--- a/src/bin/lttng/commands/destroy.c
+++ b/src/bin/lttng/commands/destroy.c
 <at>  <at>  -90,7 +90,9  <at>  <at>  static int destroy_session(struct lttng_session *session)
 	}

 	MSG("Session %s destroyed", session->name);
-	config_destroy_default();
+	if (strncmp(session->name, get_session_name(), NAME_MAX) == 0) {
+		config_destroy_default();
+	}

 	if (lttng_opt_mi) {
 		ret = mi_lttng_session(writer, session, 0);
--

-- 
1.7.10.4
Antoine Busque | 20 May 20:17 2015

[PATCH lttng-ust v2 1/2] Add ust_baddr_statedump start and end events

These events mark the beginning and end of base addresses state dump,
which happens once per traced application per session. Note that for a
given (process, session) pair, begin/end events are serialized and
will match. However, in a session, statedumps from different processes
may be interleaved. The vpid context should be used to identify which
events belong to which process.

Signed-off-by: Antoine Busque <abusque <at> efficios.com>
---
 liblttng-ust/lttng-ust-baddr.c     | 59 ++++++++++++++++++++++++++++++++++++++
 liblttng-ust/ust_baddr_statedump.h | 10 +++++++
 2 files changed, 69 insertions(+)

diff --git a/liblttng-ust/lttng-ust-baddr.c b/liblttng-ust/lttng-ust-baddr.c
index 922899b..bd3bdcb 100644
--- a/liblttng-ust/lttng-ust-baddr.c
+++ b/liblttng-ust/lttng-ust-baddr.c
 <at>  <at>  -89,6 +89,54  <at>  <at>  int trace_baddr(void *base_addr_ptr,
 }

 static
+int trace_statedump_start(void *owner)
+{
+	struct cds_list_head *sessionsp;
+	struct lttng_session *session;
+
+	if (ust_lock()) {
+		ust_unlock();
+		return 1;
+	}
+
+	sessionsp = _lttng_get_sessions();
+	cds_list_for_each_entry(session, sessionsp, node) {
+		if (session->owner != owner)
+			continue;
+		if (!session->statedump_pending)
+			continue;
+		tracepoint(ust_baddr_statedump, start,
+				session);
+	}
+	ust_unlock();
+	return 0;
+}
+
+static
+int trace_statedump_end(void *owner)
+{
+	struct cds_list_head *sessionsp;
+	struct lttng_session *session;
+
+	if (ust_lock()) {
+		ust_unlock();
+		return 1;
+	}
+
+	sessionsp = _lttng_get_sessions();
+	cds_list_for_each_entry(session, sessionsp, node) {
+		if (session->owner != owner)
+			continue;
+		if (!session->statedump_pending)
+			continue;
+		tracepoint(ust_baddr_statedump, end,
+				session);
+	}
+	ust_unlock();
+	return 0;
+}
+
+static
 int extract_soinfo_events(struct dl_phdr_info *info, size_t size, void *_data)
 {
 	int j;
 <at>  <at>  -172,6 +220,15  <at>  <at>  void dump_exec_baddr(struct extract_data *data)
 	trace_baddr(base_addr_ptr, exe_path, 0, owner);
 }

+/*
+ * Generate a statedump of base addresses of all shared objects loaded
+ * by the traced application, as well as for the application's
+ * executable itself. A statedump is delimited by start and end
+ * events. For a given (process, session) pair, begin/end events are
+ * serialized and will match. However, in a session, statedumps from
+ * different processes may be interleaved. The vpid context should be
+ * used to identify which events belong to which process.
+ */
 int lttng_ust_baddr_statedump(void *owner)
 {
 	struct extract_data data;
 <at>  <at>  -179,6 +236,7  <at>  <at>  int lttng_ust_baddr_statedump(void *owner)
 	if (getenv("LTTNG_UST_WITHOUT_BADDR_STATEDUMP"))
 		return 0;

+	trace_statedump_start(owner);
 	data.owner = owner;
 	data.exec_baddr = NULL;
 	/*
 <at>  <at>  -194,6 +252,7  <at>  <at>  int lttng_ust_baddr_statedump(void *owner)
 	 * iteration.
 	 */
 	dump_exec_baddr(&data);
+	trace_statedump_end(owner);
 	return 0;
 }

diff --git a/liblttng-ust/ust_baddr_statedump.h b/liblttng-ust/ust_baddr_statedump.h
index 77a9af4..99fb849 100644
--- a/liblttng-ust/ust_baddr_statedump.h
+++ b/liblttng-ust/ust_baddr_statedump.h
 <at>  <at>  -37,6 +37,11  <at>  <at>  extern "C" {
 #define LTTNG_UST_BADDR_STATEDUMP_PROVIDER
 #include <lttng/tracepoint.h>

+TRACEPOINT_EVENT(ust_baddr_statedump, start,
+	TP_ARGS(struct lttng_session *, session),
+	TP_FIELDS()
+)
+
 TRACEPOINT_EVENT(ust_baddr_statedump, soinfo,
 	TP_ARGS(struct lttng_session *, session, void *, baddr, const char*, sopath, int64_t, size, int64_t, mtime),
 	TP_FIELDS(
 <at>  <at>  -47,6 +52,11  <at>  <at>  TRACEPOINT_EVENT(ust_baddr_statedump, soinfo,
 	)
 )

+TRACEPOINT_EVENT(ust_baddr_statedump, end,
+	TP_ARGS(struct lttng_session *, session),
+	TP_FIELDS()
+)
+
 #endif /* _TRACEPOINT_UST_BADDR_STATEDUMP_H */

 #undef TRACEPOINT_INCLUDE
--

-- 
2.4.1
Aravind HT | 19 May 13:06 2015
Picon

lttng soft hang issue

Hi,

 

I have recently started trying lttng 2.6 for a few applications on my Ubuntu 12.04 and I noticed that the health check on sessiond and consumerd failed soon after starting the session.


On investigating, I found that thread_manage_consumer() had exited causing an overall health check failure.


Here are the sequence of steps that I found contributed to thread_manage_consumer() exiting.


1.       In thread_manage_apps() : 1558 , ust_app_unregister(pollfd) is being called. This happens when there is an error detected by revents = LTTNG_POLL_GETEV(&events, i)

My initial guess here is that as one of my apps has crashed, producing a LPOLLERR | LPOLLHUP | LPOLLRDHUP to be generated for epoll() causing ust_app_unregister() to be called for that app.

 

2.       In ust_app_unregister():3154 , close_metadata(registry, ua_sess->consumer)  in which registry->metadata_closed = 1 is set.

 

(2.a) Note: close_metadata() also calls consumer_close_metadata() which sends LTTNG_CONSUMER_CLOSE_METADATA and metadata_key to the consumerd to stop it from further dealing with the concerned app. Somehow this doesn’t seem to help.

 

3.       Next, I see that the thread_manage_consumer():1353 for some reason has ignored the above 2.a and gets to do request/reply for that app by calling ust_consumer_metadata_request():491 -> ust_app_push_metadat(ust_reg, socket,1) which at line 460 checks for registry->metadata_closed and returns an –EPIPE

 

4.       This –EPIPE error cascades all the way back up to thread_manage_consumer():1353 at which point thread_manage_consumer() decides to exit causing health_check() to fail.

 

 

So it looks like under some scenario, an application crash could cause the lttng some problems.

 

I think a possible fix for this scenario, is to instead of 4, send an ERROR message back to consumerd() . This could be done from ust_consumer_metadata_request() call. Can someone please let me know if this is correct and shed more light on the issue ?

 

 

Please forgive if there are any guideline omissions for posting here from my part. This is my first post.


Regards,

Aravind.

_______________________________________________
lttng-dev mailing list
lttng-dev <at> lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
gang li | 20 May 17:45 2015

lttng function tracing nginx problem

hi all,

I compile the nginx-1.4.7 with FLAG -finstrument-functions , and start nginx like this:

LD_PRELOAD=liblttng-ust-cyg-profile-fast.so  ./nginx


Then I use the command lttng list --userspace and got nothing like this:


UST events:

-------------

None



I don't understand why I can't get the func_exit/entry events from nginx.


By the way, I test function tracing with a single c source file and works well, output like this:


UST events:

-------------


PID: 4687 - Name: ./tt

      lttng_ust_cyg_profile:func_exit (loglevel: TRACE_DEBUG_FUNCTION (12)) (type: tracepoint)

      lttng_ust_cyg_profile:func_entry (loglevel: TRACE_DEBUG_FUNCTION (12)) (type: tracepoint)

      lttng_ust_tracef:event (loglevel: TRACE_DEBUG (14)) (type: tracepoint)

      ust_baddr_statedump:soinfo (loglevel: TRACE_DEBUG_LINE (13)) (type: tracepoint)



Wishing for help.

_______________________________________________
lttng-dev mailing list
lttng-dev <at> lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
Antoine Busque | 20 May 00:17 2015

[PATCH lttng-ust 1/2] Add ust_baddr_statedump start and end events

These events mark the beginning and end of base addresses state dump,
which happens once per traced application. Note that there is no
guarantee concerning the relative order of multiple start/end events
in the case of overlapping statedumps.  That is to say. if there are
two start events, and two end events, the first end event does not
necessarily correspond to the first start event, and similarly with
the second events.

Signed-off-by: Antoine Busque <abusque <at> efficios.com>
---
 liblttng-ust/lttng-ust-baddr.c     | 50 ++++++++++++++++++++++++++++++++++++++
 liblttng-ust/ust_baddr_statedump.h | 10 ++++++++
 2 files changed, 60 insertions(+)

diff --git a/liblttng-ust/lttng-ust-baddr.c b/liblttng-ust/lttng-ust-baddr.c
index 922899b..5ec3d40 100644
--- a/liblttng-ust/lttng-ust-baddr.c
+++ b/liblttng-ust/lttng-ust-baddr.c
 <at>  <at>  -89,6 +89,54  <at>  <at>  int trace_baddr(void *base_addr_ptr,
 }

 static
+int trace_statedump_start(void *owner)
+{
+	struct cds_list_head *sessionsp;
+	struct lttng_session *session;
+
+	if (ust_lock()) {
+		ust_unlock();
+		return 1;
+	}
+
+	sessionsp = _lttng_get_sessions();
+	cds_list_for_each_entry(session, sessionsp, node) {
+		if (session->owner != owner)
+			continue;
+		if (!session->statedump_pending)
+			continue;
+		tracepoint(ust_baddr_statedump, start,
+				session);
+	}
+	ust_unlock();
+	return 0;
+}
+
+static
+int trace_statedump_end(void *owner)
+{
+	struct cds_list_head *sessionsp;
+	struct lttng_session *session;
+
+	if (ust_lock()) {
+		ust_unlock();
+		return 1;
+	}
+
+	sessionsp = _lttng_get_sessions();
+	cds_list_for_each_entry(session, sessionsp, node) {
+		if (session->owner != owner)
+			continue;
+		if (!session->statedump_pending)
+			continue;
+		tracepoint(ust_baddr_statedump, end,
+				session);
+	}
+	ust_unlock();
+	return 0;
+}
+
+static
 int extract_soinfo_events(struct dl_phdr_info *info, size_t size, void *_data)
 {
 	int j;
 <at>  <at>  -179,6 +227,7  <at>  <at>  int lttng_ust_baddr_statedump(void *owner)
 	if (getenv("LTTNG_UST_WITHOUT_BADDR_STATEDUMP"))
 		return 0;

+	trace_statedump_start(owner);
 	data.owner = owner;
 	data.exec_baddr = NULL;
 	/*
 <at>  <at>  -194,6 +243,7  <at>  <at>  int lttng_ust_baddr_statedump(void *owner)
 	 * iteration.
 	 */
 	dump_exec_baddr(&data);
+	trace_statedump_end(owner);
 	return 0;
 }

diff --git a/liblttng-ust/ust_baddr_statedump.h b/liblttng-ust/ust_baddr_statedump.h
index 77a9af4..99fb849 100644
--- a/liblttng-ust/ust_baddr_statedump.h
+++ b/liblttng-ust/ust_baddr_statedump.h
 <at>  <at>  -37,6 +37,11  <at>  <at>  extern "C" {
 #define LTTNG_UST_BADDR_STATEDUMP_PROVIDER
 #include <lttng/tracepoint.h>

+TRACEPOINT_EVENT(ust_baddr_statedump, start,
+	TP_ARGS(struct lttng_session *, session),
+	TP_FIELDS()
+)
+
 TRACEPOINT_EVENT(ust_baddr_statedump, soinfo,
 	TP_ARGS(struct lttng_session *, session, void *, baddr, const char*, sopath, int64_t, size, int64_t, mtime),
 	TP_FIELDS(
 <at>  <at>  -47,6 +52,11  <at>  <at>  TRACEPOINT_EVENT(ust_baddr_statedump, soinfo,
 	)
 )

+TRACEPOINT_EVENT(ust_baddr_statedump, end,
+	TP_ARGS(struct lttng_session *, session),
+	TP_FIELDS()
+)
+
 #endif /* _TRACEPOINT_UST_BADDR_STATEDUMP_H */

 #undef TRACEPOINT_INCLUDE
--

-- 
2.4.1
Mathieu Desnoyers | 15 May 00:35 2015

state tracking and missing statedump end

Hi Alexandre, Hi Matthew,

You will certainly be interested in this commit in
lttng-modules:

commit 84c7055e17f9bf7628fe1004db732d932ed2a77b
Author: Mathieu Desnoyers <mathieu.desnoyers <at> efficios.com>
Date:   Thu May 14 18:29:58 2015 -0400

    Fix: missing statedump end event when block device listing available

    Incorrect handling of lttng_enumerate_block_devices() return value of 0
    (which means "ok"), causing do_lttng_statedump() to return early.

    To causes missing "lttng_statedump_end" in traces where block device
    enumeration is available (CONFIG_KALLSYMS=y).

    Reported-by: Antoine Busque <abusque <at> efficios.com>
    Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers <at> efficios.com>

Thanks,

Mathieu

--

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
Francis Rivest | 14 May 21:33 2015
Picon

(no subject)

Hello again,

We tried to install the lttng-modules-dkms package using apt and the
"ppa:lttng/ppa" repository, but we get the following information and error:

Unpacking lttng-modules-dkms (from .../lttng-modules-dkms_2.6.x+
stable+bzr727+pack22+201504291801~ubuntu12.04.1_all.deb) ...
Setting up lttng-modules-dkms
(2.6.x+stable+bzr727+pack22+201504291801~ubuntu12.04.1)
...
Loading new lttng-modules-2.6.x+stable+bzr727+pack22+201504291801~ubuntu12.04.1
DKMS files...
First Installation: checking all kernels...
Building only for 3.13.0-32-generic
Building initial module for 3.13.0-32-generic
Error! Bad return status for module build on kernel: 3.13.0-32-generic
(x86_64)
Consult /var/lib/dkms/lttng-modules/2.6.x+stable+bzr727+pack22+
201504291801~ubuntu12.04.1/build/make.log for more information.


The contain of the make.log file is the following:

DKMS make.log for
lttng-modules-2.6.x+stable+bzr727+pack22+201504291801~ubuntu12.04.1
for kernel 3.13.0-32-generic (x86_64)
Thu May 14 15:00:16 EDT 2015
make: Entering directory `/usr/src/linux-headers-3.13.0-32-generic'
/bin/sh: 1: /var/lib/dkms/lttng-modules/2.6.x+stable+bzr727+pack22+
201504291801~ubuntu12.04.1/build/abi-debian-version.sh: not found
/bin/sh: 1: /var/lib/dkms/lttng-modules/2.6.x+stable+bzr727+pack22+
201504291801~ubuntu12.04.1/build/abi-debian-version.sh: not found
   CC [M]  /var/lib/dkms/lttng-modules/2.6.x+stable+bzr727+pack22+
201504291801~ubuntu12.04.1/build/lttng-ring-buffer-client-discard.o
   CC [M]  /var/lib/dkms/lttng-modules/2.6.x+stable+bzr727+pack22+
201504291801~ubuntu12.04.1/build/lttng-ring-buffer-client-overwrite.o
   CC [M]  /var/lib/dkms/lttng-modules/2.6.x+stable+bzr727+pack22+
201504291801~ubuntu12.04.1/build/lttng-ring-buffer-metadata-client.o
   CC [M]  /var/lib/dkms/lttng-modules/2.6.x+stable+bzr727+pack22+
201504291801~ubuntu12.04.1/build/lttng-ring-buffer-client-mmap-discard.o
   CC [M]  /var/lib/dkms/lttng-modules/2.6.x+stable+bzr727+pack22+
201504291801~ubuntu12.04.1/build/lttng-ring-buffer-client-mmap-overwrite.o
   CC [M]  /var/lib/dkms/lttng-modules/2.6.x+stable+bzr727+pack22+
201504291801~ubuntu12.04.1/build/lttng-ring-buffer-metadata-mmap-client.o
   CC [M]  /var/lib/dkms/lttng-modules/2.6.x+stable+bzr727+pack22+
201504291801~ubuntu12.04.1/build/lttng-statedump-impl.o
   CC [M]  /var/lib/dkms/lttng-modules/2.6.x+stable+bzr727+pack22+
201504291801~ubuntu12.04.1/build/wrapper/irqdesc.o
   CC [M]  /var/lib/dkms/lttng-modules/2.6.x+stable+bzr727+pack22+
201504291801~ubuntu12.04.1/build/wrapper/fdtable.o
   CC [M]  /var/lib/dkms/lttng-modules/2.6.x+stable+bzr727+pack22+
201504291801~ubuntu12.04.1/build/lttng-events.o
In file included from /var/lib/dkms/lttng-modules/2.
6.x+stable+bzr727+pack22+201504291801~ubuntu12.04.1/
build/lttng-events.c:27:0:
/var/lib/dkms/lttng-modules/2.6.x+stable+bzr727+pack22+
201504291801~ubuntu12.04.1/build/wrapper/page_alloc.h:36:58: error:
operator '+' has no right operand
make[1]: *** [/var/lib/dkms/lttng-modules/2.6.x+stable+bzr727+pack22+
201504291801~ubuntu12.04.1/build/lttng-events.o] Error 1
make: *** [_module_/var/lib/dkms/lttng-modules/2.6.x+stable+bzr727+
pack22+201504291801~ubuntu12.04.1/build] Error 2
make: Leaving directory `/usr/src/linux-headers-3.13.0-32-generic'


We know that "abi-debian-version.sh" isn't found and that might be the
cause of our problem but it is supposed to be in the package...

In addition we tried to include manually this file but it didn't work.

Thanks again for helping me out.

-Francis R
_______________________________________________
lttng-dev mailing list
lttng-dev <at> lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
Francis Rivest | 14 May 15:52 2015
Picon

No kernel tracer available

Hello, I'm a student at Polytechnique Montreal and we are trying to use lttng on ubuntu(Ubuntu 14.04.2 LTS) but always encounter the same problem :

"Error: Unable to list kernel events: Kernel tracer not available"

This happens even though we are root using the command line : sudo su

We reinstalled the packages multiples time for lttng.org and from this source : https://launchpad.net/~lttng/+archive/ubuntu/ppa/

We are able to create a session but we can't enable event (kernel tracer not available) or start tracing (error : no channel found).

If someone has advice on how to deal we this, it would be appreciated a lot.

Thank you,

-Francis R.
_______________________________________________
lttng-dev mailing list
lttng-dev <at> lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Gmane