* [lttng-dev] Runtime issue with mismatched arg name in TRACEPOINT_EVENT_INSTANCE and TRACEPOINT_EVENT_CLASS
@ 2015-06-04 7:39 Eugene Ivanov
0 siblings, 0 replies; only message in thread
From: Eugene Ivanov @ 2015-06-04 7:39 UTC (permalink / raw)
Hi,
Recently I've used different names for the argument in
TRACEPOINT_EVENT_INSTANCE and TRACEPOINT_EVENT_CLASS. Everything
compiles, the probe is registered, but can't be activated.
__tracepoint_provider___probe.state is always 0 despite whatever is
shown in 'lttng list session_name'. In this case I would expect
compilation failure.
Probes example, note some_id and MISMATCHED_id:
TRACEPOINT_EVENT_CLASS(hello, myclass,
TP_ARGS(const unsigned long *, some_id),
TP_FIELDS(ctf_array(unsigned long, some_identifier, some_id, 2)))
TRACEPOINT_EVENT_INSTANCE(hello, myclass, probe_name, TP_ARGS(const
unsigned long *, MISMATCHED_id))
--
Eugene Ivanov
________________________________
This e-mail is confidential and may contain legally privileged information. It is intended only for the addressees. If you have received this e-mail in error, kindly notify us immediately by telephone or e-mail and delete the message from your system.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2015-06-04 7:39 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-06-04 7:39 [lttng-dev] Runtime issue with mismatched arg name in TRACEPOINT_EVENT_INSTANCE and TRACEPOINT_EVENT_CLASS Eugene Ivanov
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox