From: Jonathan.Haws@sdl.usu.edu (Jonathan Haws)
Subject: [lttng-dev] Issue with UST tracing - unable to view CTF traces
Date: Fri, 28 Mar 2014 16:58:51 +0000 [thread overview]
Message-ID: <7f23634aef534feaaa2083a424f38a81@Perses.usurf.usu.edu> (raw)
In-Reply-To: <CA+jJMxs5U9LHUyWm+h-dm7LuTamv7NQG4DwUSyNjFUPUvOSDNw@mail.gmail.com>
> > I am having a problem with UST tracing on my system. My setup is as follows:
> >
> > I have my development system running Xubuntu 12.04 LTS with the LTTng ppa enabled, so I am running the 2.4.0 tools. I have my embedded target running manually compiled 2.4.0 tools (it's distro is Fedora 17 right now).
> >
> > Last week things were working just fine, but I made some changes to my template file and something broke, but I can't figure out what is up.
> >
>
> What do you mean by template file?
I mean the file used to generate the source using lttng-gen-tp. That is attached.
>
> >
> > When I try to import traces into the Eclipse tools, I get the following error:
> >
> > org.eclipse.linuxtools.tmf.core.exceptions.TmfTraceException: MismatchedTokenException(LPAREN!=TERM) at metadata:204
> >
> >
> > When I try to open with babeltrace, I get the following:
> >
> > jhaws at verde:~/trace$ babeltrace sms/SMS-20110922-130857/ust
> > [error] at line 199: token "(": syntax error, unexpected LPAREN, expecting SEMICOLON or COMMA
> >
> > [error] Error creating AST
> > [warning] Unable to open trace metadata for path "sms/SMS-20110922-130857/ust/uid/0/64-bit".
> > [warning] [Context] Cannot open_trace of format ctf at path sms/SMS-20110922-130857/ust/uid/0/64-bit.
> > [warning] [Context] cannot open trace "sms/SMS-20110922-130857/ust/uid/0/64-bit" from sms/SMS-20110922-130857/ust for reading.
> > [error] Cannot open any trace for reading.
> >
> > [error] opening trace "sms/SMS-20110922-130857/ust" for reading.
> >
> > [error] none of the specified trace paths could be opened.
> >
> >
> > What am I doing wrong? Things were working great before, but now something is up. What are the chances that there is a compatibility issue between the two installations?
> >
> Could you share the trace?
Attached in zip format. Thanks!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: problem-trace.zip
Type: application/zip
Size: 48393 bytes
Desc: problem-trace.zip
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20140328/f5aa05ae/attachment-0001.zip>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: am_tpp.tp
Type: application/octet-stream
Size: 10818 bytes
Desc: am_tpp.tp
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20140328/f5aa05ae/attachment-0001.obj>
next prev parent reply other threads:[~2014-03-28 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 16:06 Jonathan Haws
2014-03-28 16:47 ` Jérémie Galarneau
2014-03-28 16:58 ` Jonathan Haws [this message]
2014-03-28 17:27 ` Jérémie Galarneau
2014-03-28 18:08 ` Jonathan Haws
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7f23634aef534feaaa2083a424f38a81@Perses.usurf.usu.edu \
--to=jonathan.haws@sdl.usu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox