* Harsh Bora (ha...@linux.vnet.ibm.com) wrote:
> On 01/10/2012 05:44 AM, Mathieu Desnoyers wrote:
>> * Harsh Bora (ha...@linux.vnet.ibm.com) wrote:
>>> On 01/09/2012 09:31 PM, Mathieu Desnoyers wrote:
* Harsh Prateek Bora (ha...@linux.vnet.ibm.com) wrote:
> Existing simple trace can log up
* Harsh Bora (ha...@linux.vnet.ibm.com) wrote:
> On 01/10/2012 01:47 AM, Alexandre Montplaisir wrote:
>> On 12-01-09 02:39 PM, Harsh Bora wrote:
>>> Hi,
>>> While building LTTng ust 1.9.4 with urcu 0.6.6, I get following
>>> compilation errors:
>>
>> Hi,
>> Did you try with the latest URCU (0.6.7)
On 01/10/2012 05:44 AM, Mathieu Desnoyers wrote:
* Harsh Bora (ha...@linux.vnet.ibm.com) wrote:
On 01/09/2012 09:31 PM, Mathieu Desnoyers wrote:
* Harsh Prateek Bora (ha...@linux.vnet.ibm.com) wrote:
Existing simple trace can log upto 6 args per trace event and does not
support strings in trac
On 01/10/2012 01:47 AM, Alexandre Montplaisir wrote:
On 12-01-09 02:39 PM, Harsh Bora wrote:
Hi,
While building LTTng ust 1.9.4 with urcu 0.6.6, I get following
compilation errors:
Hi,
Did you try with the latest URCU (0.6.7) ?
I cannot reproduce the problem here with UST 1.9.4 and URCU git h
* Harsh Bora (ha...@linux.vnet.ibm.com) wrote:
> On 01/09/2012 09:31 PM, Mathieu Desnoyers wrote:
>> * Harsh Prateek Bora (ha...@linux.vnet.ibm.com) wrote:
>>> Existing simple trace can log upto 6 args per trace event and does not
>>> support strings in trace record format. Introducing new trace fo
* David Goulet (dgou...@efficios.com) wrote:
> The check was always returning true.
>
> Signed-off-by: David Goulet
Merged, thanks!
Mathieu
> ---
> configure.ac |5 ++---
> 1 files changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/configure.ac b/configure.ac
> index 46770c5..f18d
Has anyone run lttng under fedora core 12 2.6.32.26-175.fc12.i686
Have trouble trying to figure out what to download for this kernel.
Can anyone help here ?
Thanks,
Carlo
___
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttn
The check was always returning true.
Signed-off-by: David Goulet
---
configure.ac |5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/configure.ac b/configure.ac
index 46770c5..f18d95b 100644
--- a/configure.ac
+++ b/configure.ac
@@ -102,13 +102,12 @@ AS_IF([test "x$ARCH
* Sébastien Barthélémy (barthel...@crans.org) wrote:
> Hello all,
Already fixed this morning by commit:
commit 9080554ff25b08f48762d2ee7cfa3981317e9c1d
Author: Mathieu Desnoyers
Date: Mon Jan 9 11:42:57 2012 -0500
Fix timestamps for slow-paced event rates
Given that we currently
Hello all,
I'm using LTTng 2 (only UST for now) to study the behaviour of a realtime
multiprocess application. Some of the traces I get suggest the synchronization
between the processes is not working as expected.
However this might ascome from latencies or even hops in LTTng clock source.
(Or ma
On 12-01-09 02:39 PM, Harsh Bora wrote:
> Hi,
> While building LTTng ust 1.9.4 with urcu 0.6.6, I get following
> compilation errors:
Hi,
Did you try with the latest URCU (0.6.7) ?
I cannot reproduce the problem here with UST 1.9.4 and URCU git head.
Alex
>
> CC lttng-probe-ust.lo
> CC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Sébastien,
Well, I can't recreate this problem on my side... Looking at the log you posted,
you got a successful create and after a failure or... ?
It seems that the command never reached the session daemon... and this is
*really* weird and almost
Hi,
While building LTTng ust 1.9.4 with urcu 0.6.6, I get following
compilation errors:
CC lttng-probe-ust.lo
CC lttng-context-vtid.lo
CC lttng-context-vpid.lo
CC lttng-context-pthread-id.lo
CC lttng-context-procname.lo
In file included from ../include/lttng/ust-ev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I changed a typo in the patch:
ust_ctl_register_done --> ustctl_register_done
and added your signed off:
- --> Signed-off-by: Gerlando Falauto
Merged and pushed!
Thanks a lot
David
On 12-01-05 06:25 AM, Gerlando Falauto wrote:
> When lttng-ust s
On 01/09/2012 09:31 PM, Mathieu Desnoyers wrote:
* Harsh Prateek Bora (ha...@linux.vnet.ibm.com) wrote:
Existing simple trace can log upto 6 args per trace event and does not
support strings in trace record format. Introducing new trace format as
discussed earlier on list to support variable num
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Sébastion,
Yes, any --help with a "second level" command will trigger a session daemon
exec...
It's a known """problem""". The stable release will fix that for sure.
Thanks for the report!
David
On 12-01-05 06:05 AM, Sébastien Barthélémy wrote:
* Harsh Prateek Bora (ha...@linux.vnet.ibm.com) wrote:
> Existing simple trace can log upto 6 args per trace event and does not
> support strings in trace record format. Introducing new trace format as
> discussed earlier on list to support variable number/size of arguments.
> (Ref: http://lists.gn
17 matches
Mail list logo