On 13 Nov (16:02:23), Jon Bernard wrote:
* David Goulet dgou...@efficios.com wrote:
On 03 Nov (18:19:21), Jon Bernard wrote:
* Jon Bernard jbern...@debian.org wrote:
* Mathieu Desnoyers mathieu.desnoy...@efficios.com wrote:
- Original Message -
From: Jon Bernard
Merged! Big thanks Raphaël especially for the two unit tests!
David
On 13 Nov (00:34:34), Raphaël Beamonte wrote:
David,
Please find here an updated series of patches following your
previous comments. These patches introduce updated versions of the
utils_resolve_relative and
- Original Message -
From: Raphaël Beamonte raphael.beamo...@gmail.com
To: dgou...@efficios.com
Cc: Raphaël Beamonte raphael.beamo...@gmail.com, lttng-dev@lists.lttng.org
Sent: Wednesday, November 13, 2013 12:34:37 AM
Subject: [lttng-dev] [lttng-tools PATCH 3/4] Correct the behavior
I might be missing something, but how about, instead:
1) if path start with /, directly pass it to realpath()
2) if path does not start with /, prepend getcwd() to it, and then call
realpath() on the result.
If we can do the same result as this patch without reimplementing tricky
string
On 03 Nov (18:19:21), Jon Bernard wrote:
* Jon Bernard jbern...@debian.org wrote:
* Mathieu Desnoyers mathieu.desnoy...@efficios.com wrote:
- Original Message -
From: Jon Bernard jbern...@debian.org
To: Mathieu Desnoyers mathieu.desnoy...@efficios.com
Cc: Stéphane Graber
On 07 Nov (23:32:13), Raphaël Beamonte wrote:
This functions allows to resolve relative path such as './'
and '../' inside a path string. This allows to use paths such
as '~/../test' that are received as '/home/x/../test' for
instance.
Signed-off-by: Raphaël Beamonte
, November 10, 2013 10:21:50 AM
Subject: Re: [lttng-dev] LTTng packages in Debian sid out of sync
* Mathieu Desnoyers mathieu.desnoy...@efficios.com wrote:
Hi Jon,
Thanks for the updates. Did you manage to get the upgrade path from
older lttng versions to work, or do users still need
This function aims to resolve relative path such as './' and
'../' in the middle of a path string. This allows to use paths
such as '~/../test' that are received as '/home/x/../test' for
instance.
Signed-off-by: Raphaël Beamonte raphael.beamo...@gmail.com
---
src/common/utils.c | 68
Signed-off-by: Raphaël Beamonte raphael.beamo...@gmail.com
---
.gitignore |1 +
tests/unit/Makefile.am | 15 +++--
tests/unit/test_utils_resolve_relative.c | 98 ++
tests/unit_tests |1
Even if the utils_expand_path function was intended to allow to
use unexistent directory paths, it was in fact only working for
some kind of arguments. Paths like foo, bar/ or bar/foo
when the bar directory does not exist wasn't working. This
patch introduce a new way to expand paths in this
Signed-off-by: Raphaël Beamonte raphael.beamo...@gmail.com
---
.gitignore |1 +
tests/unit/Makefile.am |7 +-
tests/unit/test_utils_expand_path.c | 170 +++
tests/unit_tests|1 +
4 files
Forgot to add lttng-tools in the subject prefix, sorry.
2013/11/13 Raphaël Beamonte raphael.beamo...@gmail.com
The warning about braces that are not necessary for any arm of a statement
should be interpreted as a warning about braces around single statements.
Signed-off-by: Raphaël Beamonte
* Mathieu Desnoyers mathieu.desnoy...@efficios.com wrote:
Hi Jon,
Thanks for the updates. Did you manage to get the upgrade path from
older lttng versions to work, or do users still need to uninstall the
old package manually ?
I'm working on the upgrade packages now. I also just noticed a
: [lttng-dev] LTTng packages in Debian sid out of sync
* Mathieu Desnoyers mathieu.desnoy...@efficios.com wrote:
Hi Jon,
Thanks for the updates. Did you manage to get the upgrade path from
older lttng versions to work, or do users still need to uninstall the
old package manually
The utils_expand_path function of lttng-tools, in src/common/utils.c,
was meant to replace the realpath(3) function of glibc in cases we
want to allow non-existing paths, such as specifying the output directory
for a trace.
While using the lttng-tools command line to create some traces, I found
This functions allows to resolve relative path such as './'
and '../' inside a path string. This allows to use paths such
as '~/../test' that are received as '/home/x/../test' for
instance.
Signed-off-by: Raphaël Beamonte raphael.beamo...@gmail.com
---
src/common/utils.c | 48
Even if the utils_expand_path function was intended to allow to
use unexistent directory paths, it was in fact only working for
some kind of arguments. Paths like foo, bar/ or bar/foo
when the bar directory does not exist wasn't working. This
patch introduce a new way to expand paths in this
Hi lttng-aficionados,
My apologies for the missing October summary, the previous months have
been pretty intense!
tl;dr : A lot of talks at LinuxCon/CloudOpen/Tracing Summit/ELCE on
LTTng; On track for mid-november 2.4 release candidate with live
streaming, Java JUL and health check in
Thanks for the update Christian!
Allow me to give a small update on the TMF (Tracing and Monitoring
Framework, a.k.a. Eclipse trace viewer) front, most of which I did talk
about in my presentation at LinuxCon.
Recent features merged in git:
- Stand-alone RCP version!
This means it's now
- Original Message -
From: Christian Babeux christian.bab...@efficios.com
To: lttng-dev@lists.lttng.org
Sent: Wednesday, November 6, 2013 5:19:45 PM
Subject: [lttng-dev] LTTng project development activities November 2013
Hi lttng-aficionados,
My apologies for the missing October
- Original Message -
From: Otavio Salvador ota...@ossystems.com.br
To: Mathieu Desnoyers mathieu.desnoy...@efficios.com
Cc: lttng-dev lttng-dev@lists.lttng.org
Sent: Thursday, October 31, 2013 2:21:21 PM
Subject: Re: lttng-modules build failure for 3.12-rc6
On Thu, Oct 31, 2013
On Mon, Nov 4, 2013 at 3:34 PM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
- Original Message -
From: Otavio Salvador ota...@ossystems.com.br
To: Mathieu Desnoyers mathieu.desnoy...@efficios.com
Cc: lttng-dev lttng-dev@lists.lttng.org
Sent: Thursday, October 31, 2013 2:21
* Jon Bernard jbern...@debian.org wrote:
* Mathieu Desnoyers mathieu.desnoy...@efficios.com wrote:
- Original Message -
From: Jon Bernard jbern...@debian.org
To: Mathieu Desnoyers mathieu.desnoy...@efficios.com
Cc: Stéphane Graber stgra...@ubuntu.com, Alexandre Montplaisir
- Original Message -
From: Otavio Salvador ota...@ossystems.com.br
To: lttng-dev lttng-dev@lists.lttng.org
Cc: Mathieu Desnoyers mathieu.desnoy...@efficios.com
Sent: Monday, October 28, 2013 9:47:01 AM
Subject: lttng-modules build failure for 3.12-rc6
Hello,
Part of build issues
On Thu, Oct 31, 2013 at 12:26 PM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
- Original Message -
From: Otavio Salvador ota...@ossystems.com.br
To: lttng-dev lttng-dev@lists.lttng.org
Cc: Mathieu Desnoyers mathieu.desnoy...@efficios.com
Sent: Monday, October 28, 2013 9:47
- Original Message -
From: Otavio Salvador ota...@ossystems.com.br
To: Mathieu Desnoyers mathieu.desnoy...@efficios.com
Cc: lttng-dev lttng-dev@lists.lttng.org
Sent: Thursday, October 31, 2013 10:30:24 AM
Subject: Re: lttng-modules build failure for 3.12-rc6
On Thu, Oct 31, 2013
On Thu, Oct 31, 2013 at 12:38 PM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
- Original Message -
From: Otavio Salvador ota...@ossystems.com.br
To: Mathieu Desnoyers mathieu.desnoy...@efficios.com
Cc: lttng-dev lttng-dev@lists.lttng.org
Sent: Thursday, October 31, 2013 10
- Original Message -
From: Otavio Salvador ota...@ossystems.com.br
To: Mathieu Desnoyers mathieu.desnoy...@efficios.com
Cc: lttng-dev lttng-dev@lists.lttng.org
Sent: Thursday, October 31, 2013 10:46:32 AM
Subject: Re: lttng-modules build failure for 3.12-rc6
On Thu, Oct 31, 2013
On Thu, Oct 31, 2013 at 4:05 PM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
...
Great; can you backport those to stable-2.3? I'd like to send the
update for Yocto including these changes and fix it for us directly
there.
Strictly speaking, supporting a new kernel can be seen
Date: Tue, 29 Oct 2013 09:50:05 +0800
However, If one more tracepoint include file(sample_tracepoint2.h) added in
app, compile failed.
compile:
gcc -I. -o sample sample.c -ldl -llttng-ust
sample.c: In function main:sample.c:12: error:
__tracepoint_sample2___bytes_in undeclared (first
- Original Message -
From: Otavio Salvador ota...@ossystems.com.br
To: Mathieu Desnoyers mathieu.desnoy...@efficios.com
Cc: Philippe Mangaud r49...@freescale.com, Daiane Angolini
daiane.angol...@freescale.com, Fabio Estevam
fabio.este...@freescale.com
Sent: Saturday, October 26,
Hello,
Part of build issues are now fixed in master (thanks Mathieu for
applying the need changes) but we're still not good:
CC [M]
* Mathieu Desnoyers mathieu.desnoy...@efficios.com wrote:
- Original Message -
From: Jon Bernard jbern...@debian.org
To: Mathieu Desnoyers mathieu.desnoy...@efficios.com
Cc: Stéphane Graber stgra...@ubuntu.com, Alexandre Montplaisir
alexmon...@voxpopuli.im,
Hi Jon,
We've had a couple of user reports about lttng versions not working in Debian.
I'm looking at the current Debian sid, and here is the situation:
http://packages.debian.org/sid/lttng-tools : version 2.1.1-2
http://packages.debian.org/sid/utils/ltt-bin : version 2.1.1-2
* Mathieu Desnoyers mathieu.desnoy...@efficios.com wrote:
Hi Jon,
We've had a couple of user reports about lttng versions not working in Debian.
I'm looking at the current Debian sid, and here is the situation:
http://packages.debian.org/sid/lttng-tools : version 2.1.1-2
- Original Message -
From: Jon Bernard jbern...@debian.org
To: Mathieu Desnoyers mathieu.desnoy...@efficios.com
Cc: Stéphane Graber stgra...@ubuntu.com, Alexandre Montplaisir
alexmon...@voxpopuli.im,
lttng-dev@lists.lttng.org
Sent: Saturday, October 19, 2013 5:10:09 PM
Subject: Re:
AM
Subject: [lttng-dev] [LTTng UST PATCH 0/2] Bug fixes for callsite
unregistering
The following two patches fix one bug each in LTTng UST.
The first patch makes sure that when a library registers callsites, those
callsites are also properly unregistered.
It is only a matter
The following two patches fix one bug each in LTTng UST.
The first patch makes sure that when a library registers callsites, those
callsites are also properly unregistered.
It is only a matter of actually updating the list of callsites during
registration.
The second patch deals with nested
Keep track of how many libraries use a tracepoint, and disable
the tracepoint when the number of users drops to zero.
A new reference counter is added to tracepoint_entry.
This keeps track of how many callsites use that tracepoint.
When you have nested libraries sharing tracepoints, you cannot
Fix the issue where the callsites are registered but never
properly unregistered.
---
liblttng-ust/tracepoint.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/liblttng-ust/tracepoint.c b/liblttng-ust/tracepoint.c
index 7bb38fa..4870d45 100644
---
This library intercept the call to close from an application and will refuse
to close it unless the call come from UST directly. The main use case is to
keep UST active in daemons which close indiscriminately all the FDs in an
arbitrary range.
This commit also add the ustclose function which sets
Signed-off-by: Yannick Brosseau yannick.bross...@gmail.com
---
src/common/testpoint/testpoint.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/common/testpoint/testpoint.h b/src/common/testpoint/testpoint.h
index dc5be83..f0d79f0 100644
---
On Thu, Sep 26, 2013 at 11:58 PM, Manikandan G em...@manikandan.co.in wrote:
Hi,
I'm using the following versions
1. lttng-modules-2.2.1
2. popt-1.16
3.userspace-rcu-0.7.6
4.lttng-tools-2.1.1
CC-ing lttng-dev.
I'd suggest you try the 2.3 release since we got rid of the metadata
timeout.
Hi,
I'm using arm cortex 9 processor and I build the lttng modules, userspace
rcu and tools using arm-linux-gnueabi toolchain.
After I compile and deployed on the target
1.
./lttng-sessiond -vvv --consumer32-path /tmp/lt
tng-build-root/lib/lttng/libexec -d
./lttng-sessiond: unrecognized option
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
___
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
Date: Thu, 26 Sep 2013 11:18:19 -0400
From: Julien Desfossez jdesfos...@efficios.com
When we issue the snapshot record command, the consumer takes the current
reading and writing positions in the ring-buffer,
and will only try to consume the data between these boundaries. It will start
at
http://www.valcartier.drdc-rddc.gc.ca/
___
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
___
lttng-dev mailing list
lttng-dev
://www.travelgis.com/map.asp?addr=918V%20QSDJ
Gouvernement du Canada | Government of Canada
http://www.valcartier.drdc-rddc.gc.ca/
___
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
___
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
On Thu, Sep 26, 2013 at 8:47 AM, Manikandan em...@manikandan.co.in wrote:
Hi,
I'm using arm cortex 9 processor and I build the lttng modules, userspace
rcu and tools using arm-linux-gnueabi toolchain.
After I compile and deployed on the target
1.
./lttng-sessiond -vvv --consumer32-path
Envoyé : 26 septembre 2013 14:33
Is the following scenario possible? The consumer tries to get_subbuf,
and is denied access (because tracers
are writing into it). It then tries to get the next sub-buffer, but the
luck of task scheduling is such that by the
time it actually calls the
Envoyé : 26 septembre 2013 15:55
If the tracers pass the consumer, and then the consumer passes the
tracers, does the consumer stop copying the buffer contents to the snapshot
trace?
* consumer reads a number of pass n sub-buffers (where n is the number of
times the tracers have gone
On 13-09-26 04:06 PM, Thibault, Daniel wrote:
Envoyé : 26 septembre 2013 15:55
If the tracers pass the consumer, and then the consumer passes the
tracers, does the consumer stop copying the buffer contents to the snapshot
trace?
* consumer reads a number of pass n sub-buffers (where
Conversely, if the session daemon catches up to the consumer daemon during
an 'lttng snapshot record' action, what happens? Does the session daemon wait
for the consumer to be done? Does the session daemon force the consumer to
wrap up prematurely? (Assuming flight recorder mode, of
Date: Mon, 23 Sep 2013 08:01:17 +
From: Ikaheimonen, JP jp_ikaheimo...@mentor.com
4) When using --exclude, the event name should be a wildcard specification,
and the excluded events should be a proper subset of the event specification.
Come to think of it, to allow exclusion of
Message: 4
Date: Mon, 23 Sep 2013 08:01:17 +
From: Ikaheimonen, JP jp_ikaheimo...@mentor.com
4) When using --exclude, the event name should be a wildcard specification,
and the excluded events should be a proper subset of the event specification.
Otherwise, a warning is given, and the
After some discussion on and off this mailing list, I present the interface to
the event exclusion feature.
Use case:
We are providing libraries for an application developer. The libraries contain
LTTng UST tracepoints, and we use them to get information about how the
application uses the
commit 9998f5216f4641a79e158135c4c1658dcc6cd2d8
Author: Mathieu Desnoyers mathieu.desnoy...@efficios.com
Date: Thu Sep 19 13:59:48 2013 -0500
LTTng trace-clock: shrink kernel blacklist
The lockup fix has been pulled into Linux master as:
commit
/lttng-dev
___
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
Hi lttng-aficionados,
August 2013 summary:
- Stable release for 2.3 (Dominus Vobiscum) : the snapshots and crash
handler are the new features for this version. See announcement [1]
for more information.
- Bug tracker cleanup has been done. Thanks to all participants.
- Minor releases:
Don't forget, it's a beer that must be made in the Quebec province and
from a microbrewery. For 2.4, the beer must begin with the letter E.
Some help:
http://www.bieresduquebec.ca/bieres
There is quite a choice, Ete indien, Elixir celeste, Ephemere... Any indication
on the character of
On Mon, Sep 9, 2013 at 4:27 PM, David Goulet dgou...@efficios.com wrote:
On 09 Sep (16:23:54), Michel Dagenais wrote:
Don't forget, it's a beer that must be made in the Quebec province and
from a microbrewery. For 2.4, the beer must begin with the letter E.
Some help:
On 09 Sep (16:23:54), Michel Dagenais wrote:
Don't forget, it's a beer that must be made in the Quebec province and
from a microbrewery. For 2.4, the beer must begin with the letter E.
Some help:
http://www.bieresduquebec.ca/bieres
There is quite a choice, Ete indien, Elixir
Hi everyone,
We've entered the 2.4 development cycle after the release of 2.3 stable
last week. The code name is still to be decided so please cast your vote
or propose new name(s) now! :)
Don't forget, it's a beer that must be made in the Quebec province and
from a microbrewery. For 2.4, the
Époque Opaque de Trou du Diable == Black IPA ;)
David
On 09 Sep (16:46:21), Jérémie Galarneau wrote:
On Mon, Sep 9, 2013 at 4:27 PM, David Goulet dgou...@efficios.com wrote:
On 09 Sep (16:23:54), Michel Dagenais wrote:
Don't forget, it's a beer that must be made in the Quebec province
2013/8/26 Mathieu Desnoyers mathieu.desnoy...@efficios.com
* Jimmy Durand Wesolowski (jimmy.durand.wesolow...@gmail.com) wrote:
2013/8/26 Mathieu Desnoyers mathieu.desnoy...@efficios.com
I got it to work. See those commits in master:
Great, thank you.
I just got a little problem
2013/8/24 Jimmy Durand jimmy.durand.wesolow...@gmail.com
2013/8/24 Mathieu Desnoyers mathieu.desnoy...@efficios.com
* Jimmy Durand (jimmy.durand.wesolow...@gmail.com) wrote:
2013/8/22 Mathieu Desnoyers mathieu.desnoy...@efficios.com
* Jimmy Durand Wesolowski
This patch adds the possibility to NOT enable given events, even if they are
covered by some wildcard specification.
When an event specification in the enable-event command starts with a '!'
character, the specification is taken to tell which events should never be
enabled.
Thus, the commands
From fef5a576084bf261b4d297f2d11843ef6bdf305b Mon Sep 17 00:00:00 2001
From: JP Ikaheimonen jp_ikaheimo...@mentor.com
Date: Thu, 22 Aug 2013 13:44:50 +0300
Subject: [PATCH] Added event exclusion
Added a new parameter to enable-event command. With this command,
you can exclude events from a
Dear Jimmy Durand,
On Sat, 24 Aug 2013 17:34:16 +0200, Jimmy Durand wrote:
What feature is this patchset adding that is not covered by the usual
approach ? Or what is it fixing ?
Actually, this is enough for a regular system build, but if you wish to
build
it in another directory with
Dear Jimmy Durand Wesolowski,
On Mon, 26 Aug 2013 09:43:49 +0200, Jimmy Durand Wesolowski wrote:
Here is a quick test, without any of my modifications. I had to pass both
CFLAGS and LDFLAGS to ./configure, as said earlier, which can be
considered
a normal process:
* Thomas Petazzoni (thomas.petazz...@free-electrons.com) wrote:
Dear Jimmy Durand Wesolowski,
On Mon, 26 Aug 2013 09:43:49 +0200, Jimmy Durand Wesolowski wrote:
Here is a quick test, without any of my modifications. I had to pass both
CFLAGS and LDFLAGS to ./configure, as said earlier,
2013/8/26 Mathieu Desnoyers mathieu.desnoy...@efficios.com
Now I just have to figure out how to teach lttng-gen-tp about CPPFLAGS
:-/
My patch is correcting this, and the new version does take your
comment into account.
Thank you,
--
Jimmy Durand Wesolowski
OpenWide RD engineer
OneAccess
* Jimmy Durand Wesolowski (jimmy.durand.wesolow...@gmail.com) wrote:
2013/8/26 Mathieu Desnoyers mathieu.desnoy...@efficios.com
Now I just have to figure out how to teach lttng-gen-tp about CPPFLAGS
:-/
My patch is correcting this, and the new version does take your
comment into
* Mathieu Desnoyers (mathieu.desnoy...@efficios.com) wrote:
* Jimmy Durand Wesolowski (jimmy.durand.wesolow...@gmail.com) wrote:
2013/8/26 Mathieu Desnoyers mathieu.desnoy...@efficios.com
Now I just have to figure out how to teach lttng-gen-tp about CPPFLAGS
:-/
My patch is
2013/8/22 Mathieu Desnoyers mathieu.desnoy...@efficios.com
* Jimmy Durand Wesolowski (jimmy.durand.wesolow...@gmail.com) wrote:
Hi,
Here are some patches to allow installing LTTng-ust out of the system
directories, ie building with ./configure --prefix, without having to
set
* Jimmy Durand (jimmy.durand.wesolow...@gmail.com) wrote:
2013/8/22 Mathieu Desnoyers mathieu.desnoy...@efficios.com
* Jimmy Durand Wesolowski (jimmy.durand.wesolow...@gmail.com) wrote:
Hi,
Here are some patches to allow installing LTTng-ust out of the system
directories, ie
2013/8/24 Mathieu Desnoyers mathieu.desnoy...@efficios.com
* Jimmy Durand (jimmy.durand.wesolow...@gmail.com) wrote:
2013/8/22 Mathieu Desnoyers mathieu.desnoy...@efficios.com
* Jimmy Durand Wesolowski (jimmy.durand.wesolow...@gmail.com) wrote:
Hi,
Here are some patches to
Hi,
Here are some patches to allow installing LTTng-ust out of the system
directories, ie building with ./configure --prefix, without having to set
C/CPP/LDFLAGS at both the configure and the make building steps.
The --with-urcu-prefix is introduced to allow passing the userspace-rcu
build
* Jimmy Durand Wesolowski (jimmy.durand.wesolow...@gmail.com) wrote:
Hi,
Here are some patches to allow installing LTTng-ust out of the system
directories, ie building with ./configure --prefix, without having to set
C/CPP/LDFLAGS at both the configure and the make building steps.
comparison table.
Any other suggestions would be greatly appreciated!
Regards,
/Jim
-Original Message-
From: Mathieu Desnoyers [mailto:mathieu.desnoy...@efficios.com]
Sent: August-21-13 10:41
To: Jim Dumont
Cc: 'lttng-dev@lists.lttng.org'
Subject: Re: [lttng-dev] LTTng UST vs Syslog
I would suggest something relatively simple and basic as far as
performance characteristics measurements goes - x apps, y traces /
second - measure CPU, memory, i/o, file size across the various
mechanisms.
Yes, something relatively simple should do. For a process writing to syslog,
you
: *Mathieu Desnoyers* mathieu.desnoy...@efficios.com
mailto:mathieu.desnoy...@efficios.com
Date: Sun, Jul 21, 2013 at 2:27 PM
Subject: [lttng-dev] LTTng snapshot howto
To: lttng-dev@lists.lttng.org mailto:lttng-dev@lists.lttng.org
Hi,
I just pushed a LTTng snapshot howto (new feature of lttng 2.3
Replace deprecated YYLEX_PARAM with %lex-param
Tested with bison 2.7 and bison 3.0
Signed-off-by: Zifei Tong soar...@gmail.com
---
src/lib/lttng-ctl/filter/filter-ast.h| 3 ---
src/lib/lttng-ctl/filter/filter-parser.y | 13 +++--
2 files changed, 7 insertions(+), 9 deletions(-)
Also tested on CentOS6 with bison 2.4
On 2013-08-16 08:05, Zifei Tong wrote:
Replace deprecated YYLEX_PARAM with %lex-param
Tested with bison 2.7 and bison 3.0
Signed-off-by: Zifei Tong soar...@gmail.com
---
src/lib/lttng-ctl/filter/filter-ast.h| 3 ---
* Zifei Tong (soar...@gmail.com) wrote:
Replace deprecated YYLEX_PARAM with %lex-param
Tested with bison 2.7 and bison 3.0
Signed-off-by: Zifei Tong soar...@gmail.com
Acked-by: Mathieu Desnoyers mathieu.desnoy...@efficios.com
David, can you take care of merging it ?
Thanks,
Mathieu
merged as:
commit 9039edd4983b46fc45dae7ed42396ef7f7e5635a
Author: Zifei Tong soar...@gmail.com
Date: Fri Aug 16 16:52:21 2013 -0400
Fix filter parser segmentation fault with bison 3.0
Replace deprecated YYLEX_PARAM with %lex-param
Tested with bison 2.4, 2.5, 2.7 and 3.0.
Since the 8692d4e lttng-tools commit (12 July), the default configuration
for user-space channels is per-UID (it would be nice if 'lttng enable-channel
--help' said so, by the way). However, in
lttng-tools\src\lib\lttng-ctl\lttng-ctl.c, one can still read:
void
Some code will be refactored to share between kernel and UST, but
before going further, I'd like to gather some feedbacks to make
sure this design is acceptable.
Thanks,
Julien
Signed-off-by: Julien Desfossez jdesfos...@efficios.com
---
include/lttng/lttng-index.h | 44
* Julien Desfossez (jdesfos...@efficios.com) wrote:
Some code will be refactored to share between kernel and UST, but
before going further, I'd like to gather some feedbacks to make
sure this design is acceptable.
Thanks,
Julien
Signed-off-by: Julien Desfossez jdesfos...@efficios.com
* Julien Desfossez (jdesfos...@efficios.com) wrote:
Some code will be refactored to share between kernel and UST, but
before going further, I'd like to gather some feedbacks to make
sure this design is acceptable.
Thanks,
Julien
Signed-off-by: Julien Desfossez jdesfos...@efficios.com
* Mathieu Desnoyers (mathieu.desnoy...@efficios.com) wrote:
* Julien Desfossez (jdesfos...@efficios.com) wrote:
[...]
+static int create_index_file(struct lttng_consumer_stream *stream)
+{
+ char *index_name;
+ struct lttng_packet_index_file_hdr hdr;
+ int ret;
+
+ ret =
On error, the ioctl kernctl_get_next_subbuf returns -1 and sets errno to
a meaningful value but we were ignoring it. It was causing
lttng_kconsumer_read_subbuffer to return -1 (error) instead of -EAGAIN
(normal).
Signed-off-by: Julien Desfossez jdesfos...@efficios.com
---
This test detects if we actually append new metadata when enabling a
kernel event after a start.
Signed-off-by: Julien Desfossez jdesfos...@efficios.com
---
tests/regression/kernel/test_event_basic | 24 +++-
1 file changed, 23 insertions(+), 1 deletion(-)
diff --git
This should have been done for 2.3-rc1.
Signed-off-by: Julien Desfossez jdesfos...@efficios.com
---
src/common/sessiond-comm/relayd.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/common/sessiond-comm/relayd.h
b/src/common/sessiond-comm/relayd.h
index
* Julien Desfossez (jdesfos...@efficios.com) wrote:
On error, the ioctl kernctl_get_next_subbuf returns -1 and sets errno to
a meaningful value but we were ignoring it. It was causing
lttng_kconsumer_read_subbuffer to return -1 (error) instead of -EAGAIN
(normal).
Merging an updated patch
* Julien Desfossez (jdesfos...@efficios.com) wrote:
This test detects if we actually append new metadata when enabling a
kernel event after a start.
merged, thanks!
Mathieu
Signed-off-by: Julien Desfossez jdesfos...@efficios.com
---
tests/regression/kernel/test_event_basic | 24
* Julien Desfossez (jdesfos...@efficios.com) wrote:
This should have been done for 2.3-rc1.
Signed-off-by: Julien Desfossez jdesfos...@efficios.com
---
src/common/sessiond-comm/relayd.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Since we heritate the relayd protocol version from the sessiond and
relayd version, use the VERSION macro instead of additionnal fields.
Signed-off-by: Julien Desfossez jdesfos...@efficios.com
---
src/bin/lttng-sessiond/cmd.c | 11 +--
src/common/sessiond-comm/relayd.h |3 ---
* Julien Desfossez (jdesfos...@efficios.com) wrote:
Since we heritate the relayd protocol version from the sessiond and
relayd version, use the VERSION macro instead of additionnal fields.
I merged these instead:
commit d83a952ce0d3a03bd3d36505d665db99b2c65fa2
Author: Mathieu Desnoyers
701 - 800 of 1165 matches
Mail list logo
