Hi Mathieu,
On 12.06.2017 18:08, Mathieu Desnoyers wrote:
I'm struggling to get lttng to run on an i.MX 25 board. I got everything
working, however the timestamps in the resulting trace file are all the
same. Because of the timestamps, TraceCompass fails at visualizing the
schedule.
I record on
I am using the babeltrace python3 bindings on a trace collected with
event-loss-mode
set to discard. The tracecollection is a combination of a kernel channel and a
usermode
channel. How can I tell whether there are any lost events in this trace?
-- Tom Deneau
__
On Mon, Jun 12, 2017 at 6:21 PM, Deneau, Tom wrote:
>
> I am using the babeltrace python3 bindings on a trace collected with
> event-loss-mode
> set to discard. The tracecollection is a combination of a kernel channel and
> a usermode
> channel. How can I tell whether there are any lost events
Merged in master and stable-2.10 with a change. Read on.
Thanks!
Jérémie
On 2 June 2017 at 14:52, Jonathan Rajotte
wrote:
> Fixes CID #1375913, 1375912, 1375911 1375910 1375909 1375908
>
> Signed-off-by: Jonathan Rajotte
> ---
> tests/regression/tools/notification/base_client.c | 25
> ++
Merged in stable-1.5. Thanks!
Jérémie
On 2 June 2017 at 11:56, Michael Jeanson wrote:
> Turns out that contrary to what is documented some versions of distutils
> don't honor the LIBS variable, use LDFLAGS instead.
>
> Signed-off-by: Michael Jeanson
> ---
> bindings/python/Makefile.am | 3 +--
Merged in master and stable-2.10. Thanks!
Jérémie
On 16 May 2017 at 16:55, Jonathan Rajotte
wrote:
> v2: missing "channel" in commit title.
>
> Keep the publishing state to the notification thread of the channel
> object. Issue remove command if the channel was previously
> published.
>
> Fixes
Merged in master and stable-2.10 with modifications. Thanks!
I'll also add a check on trigger registration.
Jérémie
On 15 May 2017 at 15:37, Jonathan Rajotte
wrote:
> The RING_BUFFER_SNAPSHOT_SAMPLE_POSITIONS was introduced in
> lttng-modules ABI version 2.3. When interacting with a kernel trac
Jérémie Galarneau writes:
> Known limitations
> -
>
> Being a "pre" release, a number of features are still in active development
> and
> bugs are being worked on.
>
> This first release does not expose the Python packages (present in the Git
> tree)
> as we are reworking them to
On 13 June 2017 at 13:18, Nathan Lynch wrote:
> Jérémie Galarneau writes:
>> Known limitations
>> -
>>
>> Being a "pre" release, a number of features are still in active development
>> and
>> bugs are being worked on.
>>
>> This first release does not expose the Python packages (
On 2017-06-13 20:38, Jérémie Galarneau wrote:
FYI, the in-tree plugins are embed-able by setting
BT_BUILT_IN_PLUGINS=1 at configure time.
I was wondering why this was an environment variable and not a command
line flag to configure. I find env var-related problems more difficult
to diagnose
On 13 June 2017 at 15:04, Simon Marchi wrote:
> On 2017-06-13 20:38, Jérémie Galarneau wrote:
>>
>> FYI, the in-tree plugins are embed-able by setting
>> BT_BUILT_IN_PLUGINS=1 at configure time.
>
>
> I was wondering why this was an environment variable and not a command line
> flag to configure.
I am trying to use lttng to simultaneously trace some kernel and user events.
The kernel events are a few syscalls (sendto, futex).
The user events are the pthread ones in lttng-ust-libc-wrapper.
Looking for recommended lttng configurations to:
* avoid dropping any events
* avoid too much ov
On 2017-06-13 14:38, Jérémie Galarneau wrote:
>> Where can I find the Windows/mingw patches?
>
> A fair number of them are in this pull request:
> https://github.com/efficios/babeltrace/pull/56
>
> Michael (CC-ed) is still re-working/cleaning some patches on his end.
> I don't know if it's in a s
13 matches
Mail list logo
