Re: [RELEASE] LTTng-tools 2.1.0-rc1

Re: [RELEASE] LTTng-tools 2.1.0-rc1

[Bernd Hufmann]

Hi David

I've just installed LTTng-tools 2.1.0-rc1 and I wanted to use it with 
the Eclipse LTTng tracer control. First, I added 2.1.x as supported 
version to Eclipse and
then I tried to used it with 2.0.x features. I noticed a few differences 
in the output strings of command outputs [1] as well as the directory 
structure of
generated traces [2]. The Eclipse LTTng tracer control parses the String 
output of the commands to extract relevant information.

Generally, it would be much easier to maintain the Eclipse LTTng tracer 
control if for existing features the string outputs and the directory 
structure are the same
as before. Please note, if someone uses scripts to generate traces the 
output format is also important.

[1] Command output of lttng create mysession:
In v2.0.x the output was:
Session mysession created.
Traces will be written in /home/user/lttng-traces/mysession-20120314-132824

in v2.1.x the output is:
Trace(s) output set to /home/user/lttng-traces/mysession-20120822-082243
Session mysession created.

So, the first and second line are swapped. Also the content of the line 
with the path is changed. Would it be possible, to have the same order 
of the lines and same output as in v2.0.x?

[2] Trace directory structure:
I noticed that the UST traces are moved under another sub-directory.

In v2.0.x the directory structure looked as follows:
/home/user/lttng-traces/
             |-mysession-20120314-132824
                     |-kernel
                          |---<kernel trace files>
                     |-ust
                          |---<programA-<PID>-<date>>
                                           |-----------<program A 
specific trace files>

In v2.1.x the directory structure looked as follows:
/home/user/lttng-traces/
            |-mysession-20120314-132824
                     |-kernel
                          |---<kernel trace files>
                     |-ust
                          |--- mysession-20120314-132824
                                   |---<programA-<PID>-<date>>
                                           |-----------<program A 
specific trace files>

So as you see, under ust there is another sub directory with trace 
session name and date/time. I don't see a practical reason to have this 
sub directory, because the session name and date/time is already known 
from the top-level directory. Is it possible to revert this back? In 
Eclipse I would have to implement a special case for different 
LTTng-tools versions (in the import dialog).

Thank you very much in advance.

Best Regards
Bernd


On 08/17/2012 04:11 PM, David Goulet wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Greetings everyone (including LTTng elves),
>
> The lttng-tools project provides a session daemon (lttng-sessiond)
> that acts as a tracing registry, the "lttng" command line for tracing
> control, a lttng-ctl library for tracing control and a lttng-relayd
> for network streaming.
>
> This is the first release candidate for lttng-tools 2.1 which brings
> two exciting new features, network streaming and filtering support.
>
> It's the combination of a lot of work from the LTTng team so please,
> to help us improve our tools, report any bugs or misbehaving
> feature(s) that you may encounter through this mailing list or the bug
> tracker (https://bugs.lttng.org).
>
> - From now on, lttng-tools is in feature freeze mode unless an *IMMENSE*
> show stopper is found.
>
> 2012-08-17 lttng-tools 2.1.0-rc1
>      * Feature: Network Streaming
>      * Add the lttng-relayd binary for network streaming
>      * Support user space tracer filtering
>      * Multiple fixes
>
> Project website: http://lttng.org/lttng2.0
> Download link:
> http://lttng.org/files/lttng-tools/lttng-tools-2.1.0-rc1.tar.bz2
>
> Cheers!
> David
> -----BEGIN PGP SIGNATURE-----
>
> iQEcBAEBCgAGBQJQLqWLAAoJEELoaioR9I023WUH+gNuU+NL0gZInlFbFiqGG5n8
> DyvtZaUOtHr7ZoSU2cmEcNfgxzOj0jTt5lGPm7EaU7X5OUiQCiu8gz5kKsL0h5PW
> UPZ7DbGHxv8JQQCt/Ac6cydlOjbRT1fB/5GXGT+OX+g/Xzp+Utb6vrTCWCC0RvSO
> 01U2NK2+IWTuRTol7ykK1WWqTStQSKPZ6ncdYjgq1FJu2gakQA4RnhblMbXWCuP9
> EZPxafSaH19mHlhDiDmtdTl7hcWTPAd0u+qNoq7kmh+stcNSn2zjv/bNldbNfaHI
> m0kfl8NferiyRpyeD4CgNtFE5W4jm29NId7IRI14/Ow8psZegF8SNlAL76Puqo8=
> =PU4p
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Re: [RELEASE] LTTng-tools 2.1.0-rc1

[David Goulet]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi Bernd,

Comments below.

Bernd Hufmann:
> Hi David
> 
> I've just installed LTTng-tools 2.1.0-rc1 and I wanted to use it
> with the Eclipse LTTng tracer control. First, I added 2.1.x as
> supported version to Eclipse and then I tried to used it with 2.0.x
> features. I noticed a few differences in the output strings of
> command outputs [1] as well as the directory structure of generated
> traces [2]. The Eclipse LTTng tracer control parses the String 
> output of the commands to extract relevant information.
> 
> Generally, it would be much easier to maintain the Eclipse LTTng
> tracer control if for existing features the string outputs and the
> directory structure are the same as before. Please note, if someone
> uses scripts to generate traces the output format is also
> important.
> 
> [1] Command output of lttng create mysession: In v2.0.x the output
> was: Session mysession created. Traces will be written in
> /home/user/lttng-traces/mysession-20120314-132824
> 
> in v2.1.x the output is: Trace(s) output set to
> /home/user/lttng-traces/mysession-20120822-082243 Session mysession
> created.
> 
> So, the first and second line are swapped. Also the content of the
> line with the path is changed. Would it be possible, to have the
> same order of the lines and same output as in v2.0.x?

Hmmmm, that's a fair point. Normally I would *strongly* recommand you
use "lttng list mysession" to get the output path but still, we could
make the argument that the output of the "create" command should not
changed between minor version.

> 
> [2] Trace directory structure: I noticed that the UST traces are
> moved under another sub-directory.
> 
> In v2.0.x the directory structure looked as follows: 
> /home/user/lttng-traces/ |-mysession-20120314-132824 |-kernel 
> |---<kernel trace files> |-ust |---<programA-<PID>-<date>> 
> |-----------<program A specific trace files>
> 
> In v2.1.x the directory structure looked as follows: 
> /home/user/lttng-traces/ |-mysession-20120314-132824 |-kernel 
> |---<kernel trace files> |-ust |--- mysession-20120314-132824 
> |---<programA-<PID>-<date>> |-----------<program A specific trace
> files>

This is absolutely not suppose to be like that... I'm unable to
reproduce this behavior having the "mysession-**" created two times.

Can you give me the exact series of command you do to get this
directory structure?

The normal case and wht 2.1.x should to is provide you the same
directory structure as 2.0.x. Ex:

~/lttng-traces/test-20120822-091412/ust/lt-hello-4542-20120822-091415

Thanks!
David

> 
> So as you see, under ust there is another sub directory with trace 
> session name and date/time. I don't see a practical reason to have
> this sub directory, because the session name and date/time is
> already known from the top-level directory. Is it possible to
> revert this back? In Eclipse I would have to implement a special
> case for different LTTng-tools versions (in the import dialog).
> 
> Thank you very much in advance.
> 
> Best Regards Bernd
> 
> 
> On 08/17/2012 04:11 PM, David Goulet wrote: Greetings everyone
> (including LTTng elves),
> 
> The lttng-tools project provides a session daemon (lttng-sessiond) 
> that acts as a tracing registry, the "lttng" command line for
> tracing control, a lttng-ctl library for tracing control and a
> lttng-relayd for network streaming.
> 
> This is the first release candidate for lttng-tools 2.1 which
> brings two exciting new features, network streaming and filtering
> support.
> 
> It's the combination of a lot of work from the LTTng team so
> please, to help us improve our tools, report any bugs or
> misbehaving feature(s) that you may encounter through this mailing
> list or the bug tracker (https://bugs.lttng.org).
> 
> - From now on, lttng-tools is in feature freeze mode unless an
> *IMMENSE* show stopper is found.
> 
> 2012-08-17 lttng-tools 2.1.0-rc1 * Feature: Network Streaming * Add
> the lttng-relayd binary for network streaming * Support user space
> tracer filtering * Multiple fixes
> 
> Project website: http://lttng.org/lttng2.0 Download link: 
> http://lttng.org/files/lttng-tools/lttng-tools-2.1.0-rc1.tar.bz2
> 
> Cheers! David
>> 
>> _______________________________________________ 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@lists.lttng.org 
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJQNN0vAAoJEELoaioR9I02VxMH/jQkvukB85gPaAiirzf5P2Zo
0cudVwdvCuK+43mFUsuN9l7FQh0MKjplWtpqDHDqc1uxgQ7MAGnD+ZzHY347qGVx
Qdcrn+DBUIeawExfqrqRNZZpiQnKGf4dp0TkQNBHiq72ymVHd3lXCT8NPbrBn8T2
9v0FRgLZW29Z/M87I71n5JfPMrg5iU8e8bcNnl1gEL+rCe26Sxb+1MPtmQ3s7XSa
DYCwYxrWQsCJUxqAfIP4CJQasPiYwPFb3uCyTw5zf6YO+8jpVQOEN5XF6hAsLoWK
2XLgDPCFqJAOAXjswykK5SGVw8QuawQQnsQYeG37mxB2lhe29m3JnX4gl1kKwHE=
=8KxL
-----END PGP SIGNATURE-----

Re: [RELEASE] LTTng-tools 2.1.0-rc1

[Bernd Hufmann]

Hi David

thanks for your answers. See below for more information.

\Bernd

On 08/22/2012 09:22 AM, David Goulet wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Hi Bernd,
>
> Comments below.
>
> Bernd Hufmann:
>> Hi David
>>
>> I've just installed LTTng-tools 2.1.0-rc1 and I wanted to use it
>> with the Eclipse LTTng tracer control. First, I added 2.1.x as
>> supported version to Eclipse and then I tried to used it with 2.0.x
>> features. I noticed a few differences in the output strings of
>> command outputs [1] as well as the directory structure of generated
>> traces [2]. The Eclipse LTTng tracer control parses the String
>> output of the commands to extract relevant information.
>>
>> Generally, it would be much easier to maintain the Eclipse LTTng
>> tracer control if for existing features the string outputs and the
>> directory structure are the same as before. Please note, if someone
>> uses scripts to generate traces the output format is also
>> important.
>>
>> [1] Command output of lttng create mysession: In v2.0.x the output
>> was: Session mysession created. Traces will be written in
>> /home/user/lttng-traces/mysession-20120314-132824
>>
>> in v2.1.x the output is: Trace(s) output set to
>> /home/user/lttng-traces/mysession-20120822-082243 Session mysession
>> created.
>>
>> So, the first and second line are swapped. Also the content of the
>> line with the path is changed. Would it be possible, to have the
>> same order of the lines and same output as in v2.0.x?
> Hmmmm, that's a fair point. Normally I would *strongly* recommand you
> use "lttng list mysession" to get the output path but still, we could
> make the argument that the output of the "create" command should not
> changed between minor version.
I use the list command to get the directory of a session and the session 
name. However, there are some validation done after "lttng create 
session" (e.g. check for correct session name or path). So the order of 
lines and string content is important. I already use regular expressions 
to problems with minor changes (e.g. more whitespaces), but we cannot 
foresee all cases.

As I understand the numbering scheme, the first digit is for major 
changes (non-backwards compatible, API breaking changes). The second 
digit is for non-API breaking changes including feature and API 
additions. And the last digit (minor) is for bugfixes. Since there is no 
remote protocol defined for using LTTng tools remotely, the Eclipse 
LTTng control relies on the string output of the command line tool. So, 
I consider the output as part of the API :-).

>> [2] Trace directory structure: I noticed that the UST traces are
>> moved under another sub-directory.
>>
>> In v2.0.x the directory structure looked as follows:
>> /home/user/lttng-traces/ |-mysession-20120314-132824 |-kernel
>> |---<kernel trace files>  |-ust |---<programA-<PID>-<date>>
>> |-----------<program A specific trace files>
>>
>> In v2.1.x the directory structure looked as follows:
>> /home/user/lttng-traces/ |-mysession-20120314-132824 |-kernel
>> |---<kernel trace files>  |-ust |--- mysession-20120314-132824
>> |---<programA-<PID>-<date>>  |-----------<program A specific trace
>> files>
> This is absolutely not suppose to be like that... I'm unable to
> reproduce this behavior having the "mysession-**" created two times.
>
> Can you give me the exact series of command you do to get this
> directory structure?
See below the log of commands I executed. I also added the output of 
command "find ." under lttng-traces directory. In there you see the 
additional sub-directory.
By the way, I installed lttng-tools, lttng-ust and userspace-rcu from 
source code.  Here are the corresponding SHA numbers:
lttng-tools: 68264071f9d1b789de1350cbec479b52a9b54acf
lttng-ust: 0f4eaec3e738fa0f33296a46fe08266a60787c23
userspace-rcu: 768fba83676f49eb73fd1d8ad452016a84c5ec2a


 > lttng create mysession
Trace(s) output set to /home/bernd/lttng-traces/mysession-20120822-094418
Session mysession created.

 > lttng enable-event  -a  -k
All kernel events are enabled in channel channel0

 > lttng enable-event  -a  -u
All UST events are enabled in channel channel0

 > lttng start
Tracing started for session mysession

 > lttng stop
Tracing stopped for session mysession

 > lttng destroy
Session mysession destroyed

 > find .
.
./mysession-20120822-094418
./mysession-20120822-094418/mysession-20120822-094542
./mysession-20120822-094418/mysession-20120822-094542/ust
./mysession-20120822-094418/mysession-20120822-094542/ust/lt-hello-2039-20120822-094551
./mysession-20120822-094418/mysession-20120822-094542/ust/lt-hello-2039-20120822-094551/channel0_0
./mysession-20120822-094418/mysession-20120822-094542/ust/lt-hello-2039-20120822-094551/metadata
./mysession-20120822-094418/mysession-20120822-094542/ust/lt-hello-2056-20120822-094551
./mysession-20120822-094418/mysession-20120822-094542/ust/lt-hello-2056-20120822-094551/channel0_0
./mysession-20120822-094418/mysession-20120822-094542/ust/lt-hello-2056-20120822-094551/metadata
./mysession-20120822-094418/kernel
./mysession-20120822-094418/kernel/channel0_0
./mysession-20120822-094418/kernel/metadata

> The normal case and wht 2.1.x should to is provide you the same
> directory structure as 2.0.x. Ex:
>
> ~/lttng-traces/test-20120822-091412/ust/lt-hello-4542-20120822-091415
>
> Thanks!
> David
>
>> So as you see, under ust there is another sub directory with trace
>> session name and date/time. I don't see a practical reason to have
>> this sub directory, because the session name and date/time is
>> already known from the top-level directory. Is it possible to
>> revert this back? In Eclipse I would have to implement a special
>> case for different LTTng-tools versions (in the import dialog).
>>
>> Thank you very much in advance.
>>
>> Best Regards Bernd
>>
>>
>> On 08/17/2012 04:11 PM, David Goulet wrote: Greetings everyone
>> (including LTTng elves),
>>
>> The lttng-tools project provides a session daemon (lttng-sessiond)
>> that acts as a tracing registry, the "lttng" command line for
>> tracing control, a lttng-ctl library for tracing control and a
>> lttng-relayd for network streaming.
>>
>> This is the first release candidate for lttng-tools 2.1 which
>> brings two exciting new features, network streaming and filtering
>> support.
>>
>> It's the combination of a lot of work from the LTTng team so
>> please, to help us improve our tools, report any bugs or
>> misbehaving feature(s) that you may encounter through this mailing
>> list or the bug tracker (https://bugs.lttng.org).
>>
>> - From now on, lttng-tools is in feature freeze mode unless an
>> *IMMENSE* show stopper is found.
>>
>> 2012-08-17 lttng-tools 2.1.0-rc1 * Feature: Network Streaming * Add
>> the lttng-relayd binary for network streaming * Support user space
>> tracer filtering * Multiple fixes
>>
>> Project website: http://lttng.org/lttng2.0 Download link:
>> http://lttng.org/files/lttng-tools/lttng-tools-2.1.0-rc1.tar.bz2
>>
>> Cheers! David
>>> _______________________________________________ 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@lists.lttng.org
>> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
> -----BEGIN PGP SIGNATURE-----
>
> iQEcBAEBCgAGBQJQNN0vAAoJEELoaioR9I02VxMH/jQkvukB85gPaAiirzf5P2Zo
> 0cudVwdvCuK+43mFUsuN9l7FQh0MKjplWtpqDHDqc1uxgQ7MAGnD+ZzHY347qGVx
> Qdcrn+DBUIeawExfqrqRNZZpiQnKGf4dp0TkQNBHiq72ymVHd3lXCT8NPbrBn8T2
> 9v0FRgLZW29Z/M87I71n5JfPMrg5iU8e8bcNnl1gEL+rCe26Sxb+1MPtmQ3s7XSa
> DYCwYxrWQsCJUxqAfIP4CJQasPiYwPFb3uCyTw5zf6YO+8jpVQOEN5XF6hAsLoWK
> 2XLgDPCFqJAOAXjswykK5SGVw8QuawQQnsQYeG37mxB2lhe29m3JnX4gl1kKwHE=
> =8KxL
> -----END PGP SIGNATURE-----

Re: [RELEASE] LTTng-tools 2.1.0-rc1

[David Goulet]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On 22/08/12 10:27 AM, Bernd Hufmann wrote:
> Hi David
> 
> thanks for your answers. See below for more information.
> 
> \Bernd
> 
> On 08/22/2012 09:22 AM, David Goulet wrote: Hi Bernd,
> 
> Comments below.
> 
> Bernd Hufmann:
>>>> Hi David
>>>> 
>>>> I've just installed LTTng-tools 2.1.0-rc1 and I wanted to use it with
>>>> the Eclipse LTTng tracer control. First, I added 2.1.x as supported
>>>> version to Eclipse and then I tried to used it with 2.0.x features. I
>>>> noticed a few differences in the output strings of command outputs
>>>> [1] as well as the directory structure of generated traces [2]. The
>>>> Eclipse LTTng tracer control parses the String output of the commands
>>>> to extract relevant information.
>>>> 
>>>> Generally, it would be much easier to maintain the Eclipse LTTng 
>>>> tracer control if for existing features the string outputs and the 
>>>> directory structure are the same as before. Please note, if someone 
>>>> uses scripts to generate traces the output format is also important.
>>>> 
>>>> [1] Command output of lttng create mysession: In v2.0.x the output 
>>>> was: Session mysession created. Traces will be written in 
>>>> /home/user/lttng-traces/mysession-20120314-132824
>>>> 
>>>> in v2.1.x the output is: Trace(s) output set to 
>>>> /home/user/lttng-traces/mysession-20120822-082243 Session mysession 
>>>> created.
>>>> 
>>>> So, the first and second line are swapped. Also the content of the 
>>>> line with the path is changed. Would it be possible, to have the same
>>>> order of the lines and same output as in v2.0.x?
> Hmmmm, that's a fair point. Normally I would *strongly* recommand you use
> "lttng list mysession" to get the output path but still, we could make the
> argument that the output of the "create" command should not changed between
> minor version.
>> I use the list command to get the directory of a session and the session
>> name. However, there are some validation done after "lttng create
>> session" (e.g. check for correct session name or path). So the order of
>> lines and string content is important. I already use regular expressions
>> to problems with minor changes (e.g. more whitespaces), but we cannot
>> foresee all cases.
> 
>> As I understand the numbering scheme, the first digit is for major
>> changes (non-backwards compatible, API breaking changes). The second
>> digit is for non-API breaking changes including feature and API
>> additions. And the last digit (minor) is for bugfixes. Since there is no
>> remote protocol defined for using LTTng tools remotely, the Eclipse LTTng
>> control relies on the string output of the command line tool. So, I
>> consider the output as part of the API :-).

I will have to agree on that and will change back the output. I'll make a RC2
after that.

> 
>>>> [2] Trace directory structure: I noticed that the UST traces are 
>>>> moved under another sub-directory.
>>>> 
>>>> In v2.0.x the directory structure looked as follows: 
>>>> /home/user/lttng-traces/ |-mysession-20120314-132824 |-kernel 
>>>> |---<kernel trace files>  |-ust |---<programA-<PID>-<date>> 
>>>> |-----------<program A specific trace files>
>>>> 
>>>> In v2.1.x the directory structure looked as follows: 
>>>> /home/user/lttng-traces/ |-mysession-20120314-132824 |-kernel 
>>>> |---<kernel trace files>  |-ust |--- mysession-20120314-132824 
>>>> |---<programA-<PID>-<date>>  |-----------<program A specific trace 
>>>> files>
> This is absolutely not suppose to be like that... I'm unable to reproduce
> this behavior having the "mysession-**" created two times.
> 
> Can you give me the exact series of command you do to get this directory
> structure?
>> See below the log of commands I executed. I also added the output of
>> command "find ." under lttng-traces directory. In there you see the
>> additional sub-directory. By the way, I installed lttng-tools, lttng-ust
>> and userspace-rcu from source code.  Here are the corresponding SHA
>> numbers: lttng-tools: 68264071f9d1b789de1350cbec479b52a9b54acf lttng-ust:
>> 0f4eaec3e738fa0f33296a46fe08266a60787c23 userspace-rcu:
>> 768fba83676f49eb73fd1d8ad452016a84c5ec2a
> 
> 
> lttng create mysession
>> Trace(s) output set to
>> /home/bernd/lttng-traces/mysession-20120822-094418 Session mysession
>> created.
> 
> lttng enable-event  -a  -k
>> All kernel events are enabled in channel channel0
> 
> lttng enable-event  -a  -u
>> All UST events are enabled in channel channel0
> 
> lttng start
>> Tracing started for session mysession
> 
> lttng stop
>> Tracing stopped for session mysession
> 
> lttng destroy
>> Session mysession destroyed
> 
> find .
>> . ./mysession-20120822-094418 
>> ./mysession-20120822-094418/mysession-20120822-094542 
>> ./mysession-20120822-094418/mysession-20120822-094542/ust 
>> ./mysession-20120822-094418/mysession-20120822-094542/ust/lt-hello-2039-20120822-094551
>
>>  
>> ./mysession-20120822-094418/mysession-20120822-094542/ust/lt-hello-2039-20120822-094551/channel0_0
>
>>  
>> ./mysession-20120822-094418/mysession-20120822-094542/ust/lt-hello-2039-20120822-094551/metadata
>
>>  
>> ./mysession-20120822-094418/mysession-20120822-094542/ust/lt-hello-2056-20120822-094551
>
>>  
>> ./mysession-20120822-094418/mysession-20120822-094542/ust/lt-hello-2056-20120822-094551/channel0_0
>
>>  
>> ./mysession-20120822-094418/mysession-20120822-094542/ust/lt-hello-2056-20120822-094551/metadata
>
>>  ./mysession-20120822-094418/kernel 
>> ./mysession-20120822-094418/kernel/channel0_0 
>> ./mysession-20120822-094418/kernel/metadata

There is a bug. I'll push a patch before RC2.

A wrong pointer was used during the directory setting having the wrong
behavior you are witnessing :). Good catch and thanks for the report!

Cheers
David

> 
> The normal case and wht 2.1.x should to is provide you the same directory
> structure as 2.0.x. Ex:
> 
> ~/lttng-traces/test-20120822-091412/ust/lt-hello-4542-20120822-091415
> 
> Thanks! David
> 
>>>> So as you see, under ust there is another sub directory with trace 
>>>> session name and date/time. I don't see a practical reason to have 
>>>> this sub directory, because the session name and date/time is already
>>>> known from the top-level directory. Is it possible to revert this
>>>> back? In Eclipse I would have to implement a special case for
>>>> different LTTng-tools versions (in the import dialog).
>>>> 
>>>> Thank you very much in advance.
>>>> 
>>>> Best Regards Bernd
>>>> 
>>>> 
>>>> On 08/17/2012 04:11 PM, David Goulet wrote: Greetings everyone 
>>>> (including LTTng elves),
>>>> 
>>>> The lttng-tools project provides a session daemon (lttng-sessiond) 
>>>> that acts as a tracing registry, the "lttng" command line for tracing
>>>> control, a lttng-ctl library for tracing control and a lttng-relayd
>>>> for network streaming.
>>>> 
>>>> This is the first release candidate for lttng-tools 2.1 which brings
>>>> two exciting new features, network streaming and filtering support.
>>>> 
>>>> It's the combination of a lot of work from the LTTng team so please,
>>>> to help us improve our tools, report any bugs or misbehaving
>>>> feature(s) that you may encounter through this mailing list or the
>>>> bug tracker (https://bugs.lttng.org).
>>>> 
>>>> - From now on, lttng-tools is in feature freeze mode unless an 
>>>> *IMMENSE* show stopper is found.
>>>> 
>>>> 2012-08-17 lttng-tools 2.1.0-rc1 * Feature: Network Streaming * Add 
>>>> the lttng-relayd binary for network streaming * Support user space 
>>>> tracer filtering * Multiple fixes
>>>> 
>>>> Project website: http://lttng.org/lttng2.0 Download link: 
>>>> http://lttng.org/files/lttng-tools/lttng-tools-2.1.0-rc1.tar.bz2
>>>> 
>>>> Cheers! David
>>>>> _______________________________________________ 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@lists.lttng.org 
>>>> 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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBAgAGBQJQNQFJAAoJEELoaioR9I02XnEH/AlGnn2oryRAA5FWihIt+gcN
5Mk4Ry/6iCCeIvFBwqtZpG+ATG8hBBouzAopjfRMs0tzZSVxs4Nq+jLJchTD8Igh
mPJyXhorBo4nCXFsH1FVaduQzTwos8hxsH2htpS6YU3DJhR4kLaVR8Qnk1Gt6t9q
HoeoXFGwaP51NHrL9m4pMvdrlUTBOFkYYTeBLrUPV/ikmkhXwmSsnQZzGsFCMphE
Qb9jEr1QebvyEk7CAocaKUMjh37j+qpaLQeOUYch6YdK+kuurotqgWqMWi/9a+UF
F+/I5wvParmN6VyWcEfo4fUqlP/4x09x1tbOyyjYf/EQ8v5PKfO7gp62xV1QRzM=
=E6zS
-----END PGP SIGNATURE-----

Fwd: [RELEASE] LTTng-tools 2.1.0-rc2

[David Goulet]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greetings everyone,

The lttng-tools project provides a session daemon (lttng-sessiond)
that acts as a tracing registry, the "lttng" command line for tracing
control, a lttng-ctl library for tracing control and a lttng-relayd
for network streaming.

This is the release candidate version 2 for lttng-tools.

2012-08-22 lttng-tools 2.1.0-rc2
        * Fix: put back 2.0 output text for lttng create cmd
        * Fix: remove set subdir call that uses bad ptr
        * Filter: Handle the unary bitwise not operator (~) with an unsupported
        * Fix: missing mutex unlock on register consumer err
        * Remove underscore from ifndef of lttng.h
        * Remove unused define in lttng.h
        * Standardize lttng command line usage text
        * Merge duplicate code in consumer for destroy relayd
        * Merge duplicate code in consumer for add relayd
        * Fix: Possible buffer overflows in strncat() usage
        * Move code out of main.c and fix some issues

Project website: http://lttng.org/lttng2.0
Download link: http://lttng.org/files/lttng-tools/lttng-tools-2.1.0-rc2.tar.bz2

Cheers!
David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBAgAGBQJQNQy4AAoJEELoaioR9I02RjQH+QGN3zpCpqjQ4s752ZtvFHd7
dthbrg/DhhSSew5YUBB4Wx7sQbGxG4RM3EATlzr482CmxqLmQpoWEl2PBtxJ762I
91PXm4+mwya0SIk8c70U+7/kNGT4ofBhmNwFOKxrNBAPnicxADZMP9n/w8IoJxFL
dh9GawjqfRmftLltPQlYRAdbfoj5P+4KCwi+dWHMguSSpQK2shMN7f4DmSf8L/fY
X1Z92NYV2I5Ez1/prAUKMh912yEQnKmH8d7bg7grMt92O2noBXRW5mldPw9p8MVV
NWpGqV4vSpw8dy7zseWpCJ/YfJETEOv9Zdcu15Asfj/izoiQxOW/5k0WMetGl1s=
=HZNa
-----END PGP SIGNATURE-----

Re: Fwd: [RELEASE] LTTng-tools 2.1.0-rc2

[Bernd Hufmann]

Hi David

I tried RC2 and I was able to create a session and to import traces 
remotely with the current Eclipse Tracer Control. I only had to change 
the supported version in the Eclipse Tracer control. Thanks for the 
updates.
I'll do some more tests. I'll let you know in case I find something else.

Best Regards
Bernd

On 08/22/2012 12:45 PM, David Goulet wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Greetings everyone,
>
> The lttng-tools project provides a session daemon (lttng-sessiond)
> that acts as a tracing registry, the "lttng" command line for tracing
> control, a lttng-ctl library for tracing control and a lttng-relayd
> for network streaming.
>
> This is the release candidate version 2 for lttng-tools.
>
> 2012-08-22 lttng-tools 2.1.0-rc2
>          * Fix: put back 2.0 output text for lttng create cmd
>          * Fix: remove set subdir call that uses bad ptr
>          * Filter: Handle the unary bitwise not operator (~) with an unsupported
>          * Fix: missing mutex unlock on register consumer err
>          * Remove underscore from ifndef of lttng.h
>          * Remove unused define in lttng.h
>          * Standardize lttng command line usage text
>          * Merge duplicate code in consumer for destroy relayd
>          * Merge duplicate code in consumer for add relayd
>          * Fix: Possible buffer overflows in strncat() usage
>          * Move code out of main.c and fix some issues
>
> Project website: http://lttng.org/lttng2.0
> Download link: http://lttng.org/files/lttng-tools/lttng-tools-2.1.0-rc2.tar.bz2
>
> Cheers!
> David
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
>
> iQEcBAEBAgAGBQJQNQy4AAoJEELoaioR9I02RjQH+QGN3zpCpqjQ4s752ZtvFHd7
> dthbrg/DhhSSew5YUBB4Wx7sQbGxG4RM3EATlzr482CmxqLmQpoWEl2PBtxJ762I
> 91PXm4+mwya0SIk8c70U+7/kNGT4ofBhmNwFOKxrNBAPnicxADZMP9n/w8IoJxFL
> dh9GawjqfRmftLltPQlYRAdbfoj5P+4KCwi+dWHMguSSpQK2shMN7f4DmSf8L/fY
> X1Z92NYV2I5Ez1/prAUKMh912yEQnKmH8d7bg7grMt92O2noBXRW5mldPw9p8MVV
> NWpGqV4vSpw8dy7zseWpCJ/YfJETEOv9Zdcu15Asfj/izoiQxOW/5k0WMetGl1s=
> =HZNa
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

[RELEASE] LTTng-tools 2.1.0-rc5

[David Goulet]

Greetings everyone (including LTTng elves),

The lttng-tools project provides a session daemon (lttng-sessiond)
that acts as a tracing registry, the "lttng" command line for tracing
control, a lttng-ctl library for tracing control and a lttng-relayd
for network streaming.

This release candidate version contains a lot of fixes and especially
one that fix the lttng_stop_tracing() behavior by adding a new call to
the API (lttng.h).

Here goes. The lttng_stop_tracing() API call, once it returns, there was
suppose to be a guarantee that the tracing data is available for
processing i.e. that any viewer/reader could parse the trace files
without any problem or missing data. We've fixed that with a new API
call, lttng_data_available(). It returns 1 if the data is ready to be
read for a tracing session (for every domain) or else 0. We've added
this call to lttng_stop_tracing() in order for this call to return
*only* if the condition is true (1). It changes the old behavior since
now the stop tracing call can wait an arbitrary amount of time.

Note that, for now, lttng_data_available is called every 2usec on the
client side (liblttng-ctl). So, this call does NOT block nor makes the
session daemon wait for data availability.

We've also added the lttng_stop_tracing_no_wait() that behaves *exactly*
like lttng_stop_tracing() but will NOT wait for data availability.

This is of course integrated in lttng command line and works for both
local consumer (on the file system) or network streaming. For the lttng
UI to _not_ wait when stopping a session, the --no-wait option was added
to "lttng stop".

Here is an example of the expected output of the command line. Each dot
"." is a 2usec period of time.

$ lttng stop mysession
Waiting for data availability....
Tracing stopped for session mysession

We know that this is a big addition to the RC process of lttng-tools but
the data availability on stop tracing is a *very* important aspect of
the lttng tool chain hence fixing it before the stable version
especially with the network streaming support.

Apart from that, here is the ChangeLog for 2.1.0-rc5 which contains a
lot of fixes and tests.

2012-10-22 lttng-tools 2.1.0-rc5
        * Fix: Remove network stream ID ABI calls
        * Tests: Add filtering tests
        * Wait for data availability when stopping a session
        * Relayd data available command support
        * Lib lttng-ctl data available command support
        * Consumer daemon data available command support
        * Add data structure for the data available command
        * Change the metadata hash table node
        * Make stream hash tables global to the consumer
        * Move add data stream to the data thread
        * Rename consumer threads and spawn them in daemon
        * Fix: relayd close stream command was not working
        * Fix: Relayd and consumerd socket leaks
        * Fix: Missing -ENODATA handling in the consumer
        * Fix: Empty metadata buffer(s) on HUP|ERR
        * ABI with support for compat 32/64 bits
        * Fix: Stream allocation and insertion consistency
        * Fix: output number of bytes written by relayd
        * Add hash table argument to helper functions
        * Fix: Add missing call rcu and read side lock
        * Tests: Fix LD_PRELOAD library lookup path for health tests
        * Fix: Add arbitrary wait period for kernel streaming test
        * Fix coding style and add/change debug statements
        * Fix: Build out of src tree
        * Tests: Add health check tests to configure
        * Tests: Add health check thread stall test
        * Tests: Add health check thread exit test
        * Tests: Add a health check utility program
        * Add testpoints in lttng-sessiond for each threads
        * New testpoint mechanism to instrument binaries for testing
        * Fix: off-by-one in comm proto between lttng-ctl and sessiond
        * Fix: Metadata stream leak when received in consumer
        * Fix: consumer_allocate_stream error handling
        * Fix: consumer should await for initial streams
        * Fix: Missing rcu read side lock in consumer

Please feel free to email the list about any questions/comments
concerning this release.

Project website: http://lttng.org/lttng2.0
Download link:
http://lttng.org/files/lttng-tools/lttng-tools-2.1.0-rc5.tar.bz2 (for
the PGP signature, same file with .asc appended)

Cheers!
David

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

[RELEASE] LTTng-tools 2.1.0-rc1

[David Goulet]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Greetings everyone (including LTTng elves),

The lttng-tools project provides a session daemon (lttng-sessiond)
that acts as a tracing registry, the "lttng" command line for tracing
control, a lttng-ctl library for tracing control and a lttng-relayd
for network streaming.

This is the first release candidate for lttng-tools 2.1 which brings
two exciting new features, network streaming and filtering support.

It's the combination of a lot of work from the LTTng team so please,
to help us improve our tools, report any bugs or misbehaving
feature(s) that you may encounter through this mailing list or the bug
tracker (https://bugs.lttng.org).

- From now on, lttng-tools is in feature freeze mode unless an *IMMENSE*
show stopper is found.

2012-08-17 lttng-tools 2.1.0-rc1
    * Feature: Network Streaming
    * Add the lttng-relayd binary for network streaming
    * Support user space tracer filtering
    * Multiple fixes

Project website: http://lttng.org/lttng2.0
Download link:
http://lttng.org/files/lttng-tools/lttng-tools-2.1.0-rc1.tar.bz2

Cheers!
David
-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJQLqWLAAoJEELoaioR9I023WUH+gNuU+NL0gZInlFbFiqGG5n8
DyvtZaUOtHr7ZoSU2cmEcNfgxzOj0jTt5lGPm7EaU7X5OUiQCiu8gz5kKsL0h5PW
UPZ7DbGHxv8JQQCt/Ac6cydlOjbRT1fB/5GXGT+OX+g/Xzp+Utb6vrTCWCC0RvSO
01U2NK2+IWTuRTol7ykK1WWqTStQSKPZ6ncdYjgq1FJu2gakQA4RnhblMbXWCuP9
EZPxafSaH19mHlhDiDmtdTl7hcWTPAd0u+qNoq7kmh+stcNSn2zjv/bNldbNfaHI
m0kfl8NferiyRpyeD4CgNtFE5W4jm29NId7IRI14/Ow8psZegF8SNlAL76Puqo8=
=PU4p
-----END PGP SIGNATURE-----