[lttng-dev] Issue with UST tracing - unable to view CTF traces

[Jérémie Galarneau]

On Fri, Mar 28, 2014 at 12:58 PM, Jonathan Haws
<Jonathan.Haws at sdl.usu.edu> wrote:
>
>> > 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!

Looking at the trace, line 199 in the metadata file immediatly stands out.

> integer { size = 32; align = 8; signed = 1; encoding = none; base = 10; } _(*__errno_location ());

The problem is that you use "errno" is your template, which is defined
by glibc as
#   define errno (*__errno_location ())

You'll have to use a different field name.

Regards,
Jérémie

-- 
Jérémie Galarneau
EfficiOS Inc.
http://www.efficios.com