From: staffan@eternaltraveller.com (Staffan Tjernstrom)
Subject: [lttng-dev] [error] at line 4295: token "(": syntax error, unexpected LPAREN, expecting SEMICOLON or COMMA
Date: Thu, 6 Oct 2016 15:14:56 -0500 [thread overview]
Message-ID: <4b4aa7c9cd3fc787af32c77c2e632a70.squirrel@email.powweb.com> (raw)
In-Reply-To: <18e9c2e74a3cf73ebf8e9f6e473de6c4@simark.ca>
> On 2016-10-06 14:14, Staffan Tjernstrom wrote:
> Hi Staffan,
>
> Are you able to provide the metadata file? Even better, would you be
> able to share your tracepoint definition file?
>
> Simon
>
Hi Simon,
Here's one of the pid's metadata files, it does look a bit suspicious
to my untrained eye. I've also enclosed the three tracepoint
definition files that are in play.
One thing to be aware of is that our application suite is in C++, so
we have mangled symbols in the definitions.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: definitions.tar.bz2
Type: application/x-bzip
Size: 8673 bytes
Desc: not available
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20161006/8ae9a17c/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: metadata.bz2
Type: application/x-bzip
Size: 6088 bytes
Desc: not available
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20161006/8ae9a17c/attachment-0003.bin>
next prev parent reply other threads:[~2016-10-06 20:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 18:14 Staffan Tjernstrom
2016-10-06 19:37 ` Mathieu Desnoyers
[not found] ` <18e9c2e74a3cf73ebf8e9f6e473de6c4@simark.ca>
2016-10-06 20:14 ` Staffan Tjernstrom [this message]
2016-10-06 20:47 ` Mathieu Desnoyers
2016-10-06 20:50 ` Mathieu Desnoyers
2016-10-06 23:02 ` Staffan Tjernstrom
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=4b4aa7c9cd3fc787af32c77c2e632a70.squirrel@email.powweb.com \
--to=staffan@eternaltraveller.com \
/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