technology.linux-distros Committers,
This automatically generated message marks the PMC's approval of the vote
for Chris Aniszczyk's full Committer status on the technology.linux-distros
project. The next step is for the project lead to return to the portal and
fill in the CVS package and employer
technology.linux-distros Committers,
This automatically generated message marks the successful completion of
voting for Chris Aniszczyk to receive full Committer status on the
technology.linux-distros project. The next step is for the PMC to approve
this vote, followed by the EMO processing the pap
Hello again everyone,
Well, thanks to Matthew for helping me out with examples and binaries and such
in my quest to figure this out. As it turns out, the problem is some very
hairy issue with library binaries that appears to occur depending on sequencing
of installing vmware tools on a Linux g
The trace you sent works fine here for me. But I will send another one.
Check your email in 3 min.
On 11-03-17 11:48 AM, Aaron Spear wrote:
The package name recently changed for the trace reader library in the
PPA, because the debian maintainer updated it. Make sure this package is
installed:
The packages install to /usr/lib so be you need to launch eclipse naked.
(no ld_library_path)
On 11-03-17 11:33 AM, Aaron Spear wrote:
Hi Francois (and Francis and Matthew)
Thanks much for looking at it. Note that I was setting
LD_LIBRARY_PATH in the shell before launching eclipse (couldn’t
> The package name recently changed for the trace reader library in the
> PPA, because the debian maintainer updated it. Make sure this package is
> installed:
>
> liblttvtraceread-loader-2.6
>
> That should solve your issue.
>
> Cheer,
>
> Francis
Well, this is very strange. I moved the libr
Hi Francois (and Francis and Matthew)
Thanks much for looking at it. Note that I was setting LD_LIBRARY_PATH in the
shell before launching eclipse (couldn't get it to work at all without that).
I also did attempt to build the trace reading libs in the right order according
to the docs, see my
Addendum:
I just loaded an experiment with v2.3/2.5 and 2.6 LTTng and UST mixed
traces and it works fine.
On 11-03-17 11:14 AM, Matthew Khouzam wrote:
Hi Aaron,
I got your trace to work by using the same package
(liblttvtraceread-loader-2.6)
I can confirm that the other trace formats (2.5 an
Hi Aaron,
I got your trace to work by using the same package
(liblttvtraceread-loader-2.6)
I can confirm that the other trace formats (2.5 and 2.3 ) load too.
For the other format, the following must be installed:
liblttvtraceread-2.3 liblttvtraceread-2.5 liblttvtraceread-2.3-jni
liblttvtra
On Thu, 2011-03-17 at 09:21 -0400, Francois Chouinard wrote:
> Hi Aaron,
>
>
> The exception you get suggests that the trace header was not read
> successfully (it reports v0.0 instead of v2.6) by the parser loader.
>
> If however I try to open these traces with the Eclipse view
Hi Aaron,
The exception you get suggests that the trace header was not read
successfully (it reports v0.0 instead of v2.6) by the parser loader.
We have an open bug for a similar situation (
https://bugs.eclipse.org/bugs/show_bug.cgi?id=315604).
A word of explanation:
To save time, we did not r
Hi guys,
I have a question about trace reading libraries and compatible versions. I
have Helios SR2 linuxtools installed, and followed the instructions on the wiki
to build the latest snapshots of both the 2.5 and 2.6 trace libraries and
installed them. With the Eclipse viewer I can import a
12 matches
Mail list logo
