Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] [error] at line 4295: token "(": syntax error, unexpected LPAREN, expecting SEMICOLON or COMMA
Date: Thu, 6 Oct 2016 20:47:48 +0000 (UTC)	[thread overview]
Message-ID: <1660413456.49151.1475786868858.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <4b4aa7c9cd3fc787af32c77c2e632a70.squirrel@email.powweb.com>

----- On Oct 6, 2016, at 4:14 PM, Staffan Tjernstrom staffan at eternaltraveller.com wrote:

>> 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.

See

TRACEPOINT_EVENT(
   sapphire,
   ip_error,
   TP_ARGS(
      int, lineno_arg,
      int, socket_arg,
      int, errno_arg
     ),
   TP_FIELDS(
ctf_integer( int, source_line, lineno_arg )
      ctf_integer( int, socket, socket_arg )
      ctf_integer( int, errno, errno_arg )
      ctf_string( error_text, strerror( errno_arg ) )
      )
   )
TRACEPOINT_LOGLEVEL( sapphire, ip_error, TRACE_ERR )

It maps to this in the metadata at line 4295:
event {
        name = "sapphire:ip_error3";
        id = 349;
        stream_id = 0;
        loglevel = 13;
        fields := struct {
                integer { size = 32; align = 8; signed = 1; encoding = none; base = 10; } _source_line;
                string _address;
                integer { size = 32; align = 8; signed = 1; encoding = none; base = 10; } _port;
                integer { size = 32; align = 8; signed = 1; encoding = none; base = 10; } _(*__errno_location ());
                string _error_text;
        };
};

I suspect that "error_text" is actually a C++ macro that maps to "(*__errno_location ())",
which is unexpected.

Thanks,

Mathieu

> 
> 
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com


  reply	other threads:[~2016-10-06 20:47 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
2016-10-06 20:47     ` Mathieu Desnoyers [this message]
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=1660413456.49151.1475786868858.JavaMail.zimbra@efficios.com \
    --to=mathieu.desnoyers@efficios.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