How to solve the coupling between libtraceevent and kernel trace?

[Lv Ying <lvying6@xxxxxxxxxx>]

Hi, all:

I am a rasdaemon developer which depeneds on libtraceevent to parse 
kernel trace events. There is coupling between libtraceevnt and kernel 
trace, if something in libtraceevent and kernel does not match, which 
will cause libtraceevent parse wrong thing. e.g 
https://github.com/mchehab/rasdaemon/pull/98

We also encounter similar problem:
* libtrace(old) KBUFFER_TYPE_TIME_STAMP size = 12
* kernel(new) KBUFFER_TYPE_TIME_STAMP size = 8
Such mismatch will cause strange behavior when parsing trace events.

So if libtraceevent is released out of(independent) kernel, how does 
libtraceevnt to keep compatible with the running kernel(maybe not the 
newest)?

--
Thanks!
Lv Ying