Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
* [ltt-dev] compiling tracepoints in UST
@ 2010-05-10  9:18 Sylvain Geneves
  2010-06-19 16:23 ` Mathieu Desnoyers
  0 siblings, 1 reply; 2+ messages in thread
From: Sylvain Geneves @ 2010-05-10  9:18 UTC (permalink / raw)


Hi,

I tried to use tracepoints with UST but i have a problem when it comes 
to compile my code...
for a better understanding, i gave it a try with the tracepoint exemple 
from the UST manual, replacing my_channel with ust and it gives the same 
thing.

Here is the content of the problematic file :

1 #include <ust/tracepoint.h>
2
3 DECLARE_TRACE(ust_myevent, TPPROTO(int v, char *st), TPARGS(v, st));


Here is the error :

tp.h:3: error: expected ?)? before ?(? token
tp.h:3: error: expected ?)? before ?(? token
tp.h:3: error: expected ?)? before ?(? token
tp.h: In function ?register_trace_ust_myevent?:
tp.h:3: error: ?probe? undeclared (first use in this function)
tp.h:3: error: (Each undeclared identifier is reported only once
tp.h:3: error: for each function it appears in.)
tp.h: At top level:
tp.h:3: error: expected ?)? before ?(? token
tp.h: In function ?unregister_trace_ust_myevent?:
tp.h:3: error: ?probe? undeclared (first use in this function)



I've got some difficulties understanding the nested macros behind 
DECLARE_TRACE, and i can't see why such an error is triggered, so if 
anyone has a clue i'd really appreciate it.

I'm using the git version of UST, and here's my output of gcc --version:
gcc (Debian 4.4.4-1) 4.4.4


Thanks in advance
Regards
Sylvain



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2010-06-19 16:23 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-05-10  9:18 [ltt-dev] compiling tracepoints in UST Sylvain Geneves
2010-06-19 16:23 ` Mathieu Desnoyers

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox