at line 4295: token "(": syntax error, unexpected LPAREN, expecting SEMICOLON or COMMA
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 19 lines · ----- On Oct 6, 2016, at 2:14 PM, Staffan Tjernstrom…
Having spent about a week moving some 1500 trace statements over to lttng, I figured it was time to try a test run. Unfortunately there seems to be a problem with the metadata.
Any clues as to what to try next?
stjernstrom@E7CH1SAPPHIRE23:~/sapphire> lttng create reg Spawning a session daemon
Session reg created.
Traces will be written in/home/stjernstrom/lttng-traces/reg-20161006-130344stjernstrom@E7CH1SAPPHIRE23:~/sapphire> lttng enable-channel -u reg --overwrite --buffers-pid -s reg --subbuf-size 1M
UST channel reg enabled for session reg stjernstrom@E7CH1SAPPHIRE23:~/sapphire> lttng add-context -u -tpthread_id
UST contextpthread_idadded to all channels stjernstrom@E7CH1SAPPHIRE23:~/sapphire> lttng enable-event -u -c reg -a All UST events are enabled in channel reg
Quoted 8 lines
stjernstrom@E7CH1SAPPHIRE23:~/sapphire> lttng start Tracing started for session reg stjernstrom@E7CH1SAPPHIRE23:~/sapphire> ${my_app} stjernstrom@E7CH1SAPPHIRE23:~/sapphire> lttng stop reg Waiting for data availability
Tracing stopped for session reg stjernstrom@E7CH1SAPPHIRE23:~/sapphire> lttng view reg Trace directory:/home/stjernstrom/lttng-traces/reg-20161006-130344
Can you provide the output of:
babeltrace -o ctf-metadata /home/stjernstrom/lttng-traces/reg-20161006-130344
?
If you can share the content of your tracepoint header files, it would also be useful.
Thanks,
Mathieu
Quoted 65 lines
[error] at line 4295: token "(": syntax error, unexpected LPAREN, expecting SEMICOLON or COMMA
[error] Error creating AST
[warning] Unable to open trace metadata for path "/home/stjernstrom/lttng-traces/reg-20161006-130344/ust/pid/cferouternode_a-2006-20161006-130611". [warning] [Context] Cannotopen_traceof format ctf at path/home/stjernstrom/lttng-traces/reg-20161006-130344/ust/pid/cferouternode_a-2006-20161006-130611. [warning] [Context] cannot open trace "/home/stjernstrom/lttng-traces/reg-20161006-130344/ust/pid/cferouternode_a-2006-20161006-130611" from/home/stjernstrom/lttng-traces/reg-20161006-130344for reading.
[error] at line 4295: token "(": syntax error, unexpected LPAREN,
expecting SEMICOLON or COMMA[error] Error creating AST
[warning] Unable to open trace metadata for path "/home/stjernstrom/lttng-traces/reg-20161006-130344/ust/pid/cmerouternode_a-2010-20161006-130611". [warning] [Context] Cannotopen_traceof format ctf at path/home/stjernstrom/lttng-traces/reg-20161006-130344/ust/pid/cmerouternode_a-2010-20161006-130611. [warning] [Context] cannot open trace "/home/stjernstrom/lttng-traces/reg-20161006-130344/ust/pid/cmerouternode_a-2010-20161006-130611" from/home/stjernstrom/lttng-traces/reg-20161006-130344for reading.
[error] at line 4295: token "(": syntax error, unexpected LPAREN,
expecting SEMICOLON or COMMA[error] Error creating AST
[warning] Unable to open trace metadata for path "/home/stjernstrom/lttng-traces/reg-20161006-130344/ust/pid/controller-2001-20161006-130602". [warning] [Context] Cannotopen_traceof format ctf at path/home/stjernstrom/lttng-traces/reg-20161006-130344/ust/pid/controller-2001-20161006-130602. [warning] [Context] cannot open trace "/home/stjernstrom/lttng-traces/reg-20161006-130344/ust/pid/controller-2001-20161006-130602" from/home/stjernstrom/lttng-traces/reg-20161006-130344for reading.
[error] at line 4295: token "(": syntax error, unexpected LPAREN,
expecting SEMICOLON or COMMA[error] Error creating AST
[warning] Unable to open trace metadata for path "/home/stjernstrom/lttng-traces/reg-20161006-130344/ust/pid/cmefeedernode_a-2013-20161006-130613". [warning] [Context] Cannotopen_traceof format ctf at path/home/stjernstrom/lttng-traces/reg-20161006-130344/ust/pid/cmefeedernode_a-2013-20161006-130613. [warning] [Context] cannot open trace "/home/stjernstrom/lttng-traces/reg-20161006-130344/ust/pid/cmefeedernode_a-2013-20161006-130613" from/home/stjernstrom/lttng-traces/reg-20161006-130344for reading.
[error] Cannot open any trace for reading.[error] opening trace "
/home/stjernstrom/lttng-traces/reg-20161006-130344" for reading.[error] none of the specified trace paths could be opened.
stjernstrom@E7CH1SAPPHIRE23:~/sapphire> lttng destroy Session reg destroyed stjernstrom@E7CH1SAPPHIRE23:~/sapphire> lttng --version lttng (LTTng Trace Control) 2.7.4 - Herbe à Détourne stjernstrom@E7CH1SAPPHIRE23:~/sapphire> uname -a
Linux E7CH1SAPPHIRE23.faction.local 4.1.13-100.fc21.x86_64 #1 SMP TueNov 10 13:13:20 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux_______________________________________________
lttng-dev mailing list
[email protected]
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
Signature · 7 lines
Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com _______________________________________________ lttng-dev mailing list [email protected] https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 8 lines · Staffan Tjernstrom
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.
_______________________________________________
lttng-dev mailing list
[email protected]
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 8 lines · ----- On Oct 6, 2016, at 4:14 PM, Staffan Tjernstrom…
Quoted 8 lines · Staffan Tjernstrom
Hi Staffan,
Are you able to provide the metadata file? Even better, would you be able to share your tracepoint definition file?
Simon
Quoted 8 lines
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
Quoted 6 lines
_______________________________________________
lttng-dev mailing list
[email protected]
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
Signature · 7 lines
Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com _______________________________________________ lttng-dev mailing list [email protected] https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 56 lines · ----- On Oct 6, 2016, at 4:47 PM, Mathieu Desnoyers…
----- On Oct 6, 2016, at 4:14 PM, Staffan Tjernstrom
Quoted 8 lines · [email protected] wrote:
Quoted 8 lines · Staffan Tjernstrom
Hi Staffan,
Are you able to provide the metadata file? Even better, would you be able to share your tracepoint definition file?
Simon
Quoted 8 lines
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; }; };
Quoted 3 lines
I suspect that "
error_text" is actually a C++ macro that maps to "(*__errno_location())",
which is unexpected.
Sorry, I meant that "error" maps to "(*__errno_location ())", in the line "ctf_integer( int, errno, errno_arg )".
Thanks,
Mathieu
Quoted 20 lines
Thanks,
Mathieu
Quoted 6 lines
_______________________________________________
lttng-dev mailing list
[email protected]
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
_______________________________________________
lttng-dev mailing list
[email protected]
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
Signature · 7 lines
Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com _______________________________________________ lttng-dev mailing list [email protected] https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 45 lines
----- On Oct 6, 2016, at 4:47 PM, Mathieu Desnoyers
Quoted 38 lines · [email protected] wrote:
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; }; };Quoted 3 lines
I suspect that "
error_text" is actually a C++ macro that maps to "(*__errno_location())",
which is unexpected.
Quoted 7 lines
Sorry, I meant that "error" maps to "(
*__errno_location())", in the line "ctf_integer( int, errno, errno_arg )".Thanks,
Mathieu
Doh, have I got egg on my face :)
errno is about as global a symbol as they come - oh well, easy fix.
Many thanks all for the prompt help.
Staffan Tj.
_______________________________________________
lttng-dev mailing list
[email protected]
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev