lttng-relayd is functional? Because I want to start it and fails with:
DEBUG3 [3661/3661]: URI string: tcp://0.0.0.0:5342 (in uri_parse() at
uri.c:250)
DEBUG3 [3661/3661]: URI dtype: 1, proto: 1, host: 0.0.0.0, subdir: , ctrl:
5342, data: 0 (in uri_parse() at uri.c:464)
DEBUG3 [3661/3661]: URI str
Hi,
I finally managed to create my trace events probes...
I copied my .h header in instrumentation/event/lttng-module and create a
lttng probe module
but now, I would like to use other channels than channel0 , how to do this,
I tried using xn_nucleus_blahblah as event name, but it has not help
uClibc does not implement posix_fallocate(), and posix_fallocate() is
mostly only an hint to the kernel that we will need such or such
amount of space inside a file. So we just don't call posix_fallocate()
when building against uClibc.
Signed-off-by: Thomas Petazzoni
---
formats/ctf/ctf.c |3
Some old compilers do not use C99 as their default C language variant,
for example gcc 4.3.x, which is used on some old machines. When such a
compiler is used, by default, ULLONG_MAX is not visible. Adding
-std=gnu99 is needed to make this definition visible.
In autoconf speak, this translates int
Good question: I don't suppose it's fully working right now, as we've
barely touched/tested it yet (we worked mostly locally or via Eclipse). It
should be amongst the next improvement batch though; could you provide the
commands you used to trigger that exact crash? I'll try to replicate it
later t
* Thomas Petazzoni (thomas.petazz...@free-electrons.com) wrote:
> uClibc does not implement posix_fallocate(), and posix_fallocate() is
> mostly only an hint to the kernel that we will need such or such
> amount of space inside a file. So we just don't call posix_fallocate()
> when building against
* Jérémie Galarneau (jeremie.galarn...@efficios.com) wrote:
> This is intended to provide a generic way to access the bt_stream_pos API
> without having to make assumptions about the output format's descriptor
> layout.
>
> Renamed format-internal.h to trace-descriptor-internal.h to make it more
* Jérémie Galarneau (jeremie.galarn...@efficios.com) wrote:
> Signed-off-by: Jérémie Galarneau
merged, thanks!
Mathieu
> ---
> formats/ctf/metadata/ctf-visitor-generate-io-struct.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/formats/ctf/metadata/ctf-visitor-generate-io-struct.c
>
* Jérémie Galarneau (jeremie.galarn...@efficios.com) wrote:
> Signed-off-by: Jérémie Galarneau
> ---
> converter/babeltrace.c | 92
> ++---
> include/babeltrace/format.h | 2 +-
> 2 files changed, 54 insertions(+), 40 deletions(-)
>
> diff --git a/c
* Jérémie Galarneau (jeremie.galarn...@efficios.com) wrote:
> Iterators now expose an event providing function so that a user does not
> need to know the input trace format to get "bt_ctf_event"s.
>
> A context can now create a specialized iterator depending on its input
> trace format.
Please re
* Thomas Petazzoni (thomas.petazz...@free-electrons.com) wrote:
> Some old compilers do not use C99 as their default C language variant,
> for example gcc 4.3.x, which is used on some old machines. When such a
> compiler is used, by default, ULLONG_MAX is not visible. Adding
> -std=gnu99 is needed
Fixes #537
Signed-off-by: Jérémie Galarneau
---
doc/examples/demo/Makefile | 4 ++--
doc/examples/easy-ust/Makefile | 4 ++--
doc/examples/hello-static-lib/Makefile | 4 ++--
3 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/doc/examples/demo/Makefile b/doc/examp
The use of LOCAL_* flags and override directives ensures that the build
succeeds even if the user explicitly overrides CFLAGS/CPPFLAGS/LDFLAGS.
Fixes #537
Signed-off-by: Jérémie Galarneau
---
doc/examples/demo/Makefile | 14 +++---
doc/examples/easy-ust/Makefile | 10
* Jérémie Galarneau (jeremie.galarn...@efficios.com) wrote:
> The use of LOCAL_* flags and override directives ensures that the build
> succeeds even if the user explicitly overrides CFLAGS/CPPFLAGS/LDFLAGS.
why use LOCAL_CPPFLAGS on one hand, but "override LDFLAGS" on the other?
What's the differ
On Tue, May 28, 2013 at 6:26 PM, Mathieu Desnoyers
wrote:
> * Jérémie Galarneau (jeremie.galarn...@efficios.com) wrote:
>> The use of LOCAL_* flags and override directives ensures that the build
>> succeeds even if the user explicitly overrides CFLAGS/CPPFLAGS/LDFLAGS.
>
> why use LOCAL_CPPFLAGS o
15 matches
Mail list logo
