On 12-04-11 06:50 PM, Mathieu Desnoyers wrote:
> With this, is the java application visible from lttng-tools before the
> first JNI call is done ?
No, not yet. This patch only adds the makefile target.
I'm still experimenting with the contents of .java file (namely, adding
support for other trace
With this, is the java application visible from lttng-tools before the
first JNI call is done ?
* Alexandre Montplaisir (alexandre.montplai...@polymtl.ca) wrote:
> Signed-off-by: Alexandre Montplaisir
> ---
> liblttng-ust-java/.gitignore|1 +
> liblttng-ust-java/LTTngUst.java |2 +-
>
Signed-off-by: Alexandre Montplaisir
---
liblttng-ust-java/.gitignore|1 +
liblttng-ust-java/LTTngUst.java |2 +-
liblttng-ust-java/Makefile.am |8 ++--
liblttng-ust-java/README|5 +
4 files changed, 13 insertions(+), 3 deletions(-)
diff --git a/liblttng-ust
Thank you -- that helped solve my problem.
Ryan Kyser
From:
Nicolas Pitre
To:
Mathieu Desnoyers
Cc:
ryan.ky...@jci.com, lttng-dev@lists.lttng.org, Avik Sil
Date:
04/10/2012 09:20 PM
Subject:
Re: [lttng-dev] ARM syscall problems
On Tue, 10 Apr 2012, Mathieu Desnoyers wrote:
> * ryan.ky.
I am getting the following kernel oops almost every time I start tracing
or event just enable events. Any ideas on how to narrow down this problem
further?
[ 136.167157] Internal error: Oops - undefined instruction: 0 [#1]
PREEMPT SMP
[ 136.174214] last sysfs file: /sys/bus/platform/drivers/f
As soon as I get everything working, I will submit the patches!
I was more concerned about the size of some of the values. For instance,
len of sys_arm_fadvise64_64 is 0xF1FF3ED8 and offset of
sys_sync_file_range2 0x1007. Both of these values seemed too
large, but now I realize
