On Tue, Jun 25, 2019 at 10:28 AM Ravindra Kumar Meena <rmeena...@gmail.com> wrote: >> >> I have only had a look at the specification, but according to >> https://diamon.org/ctf/#spec4.1.3 you can set the global "byte_order" of >> your stream in the trace description of your metadata file and override this >> default behavior for certain types. >> In the metadata file of your repository >> (https://github.com/rmeena840/rtems-tools/blob/ravindra-rtems/misc/ctf/metadata) >> you set trace to: >> trace { >> major = 1; >> minor = 8; >> byte_order = le; >> }; > > > Thank you so much, Jan Sommer, for pointing this out. > > It worked for me :). I was really struggling with it. > > Thanks > Good work, thanks Jan.
It is still confusing to me why the record event field has a different endianness than the other fields of the trace. > -- > Ravindra Kumar Meena, > B. Tech. Computer Science and Engineering, > Indian Institute of Technology (Indian School of Mines), Dhanbad > _______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
