From mboxrd@z Thu Jan  1 00:00:00 1970
From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Date: Fri, 20 Mar 2009 10:53:55 -0400
Subject: [ltt-dev] Traces data alignment
In-Reply-To: <200903200816.39240.jerome.stadelmann@heig-vd.ch>
References: <200903191606.35831.jerome.stadelmann@heig-vd.ch>
	<20090319170001.GA27344@Krystal>
	<200903200816.39240.jerome.stadelmann@heig-vd.ch>
Message-ID: <20090320145355.GA29127@Krystal>

* J?r?me Stadelmann (jerome.stadelmann at heig-vd.ch) wrote:
> On jeudi 19 mars 2009 18:00:01 Mathieu Desnoyers wrote:
> > * J?r?me Stadelmann (jerome.stadelmann at heig-vd.ch) wrote:
> > > Hi everybody,
> > > 
> > > I'm working on a LTTng traces parser and I'm a little bit blocked on the alignment. Can someone please explain how and where it is coded ?
> > 
> > The lttv lib "ltttraceread" should do that for you.
>  
> > > What are the roles of the alignment defined in the traces header and the one defined in the metadata file in the core_marker_id ?
> > > 
> > 
> > They tell that a specific tracefile content is aligned or not, and if
> > the content of a given event is aligned or not. You should really have
> > at least a look at the ltt lib traceread reference implementation.
> 
> Thank you. This library helped me a lot. I see that there is an up to 2 byte alignment in the core marker id event definition. Is there the only special case ?
> I've searched the uses of the ltt_align function. Are there other functions to look for ?
> 

Looking at ltt_align use is a good starting point.

Can you point out to the specific package/version/file/line you refer to
for the core marker id "special case" you talk about here ?

Mathieu

> Jerome
>  
> > Mathieu
> > 
> > > Regards,
> > > Jerome
> > > 
> > > _______________________________________________
> > > ltt-dev mailing list
> > > ltt-dev at lists.casi.polymtl.ca
> > > http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
> > > 
> > 
> 

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68