GSoC Project | Basic Support for Trace Compass

Ravindra Kumar Meena rmeena840 at gmail.com
Thu Jun 20 09:47:42 UTC 2019


>
> This is very good news. Writing the event stream is the easy part. Just
> fwrite() the events in the modified print_item(). Your TSDL in the metadata
> file must describe this event stream.
>
Yes. That's what I am trying today. You suggested that I have to convert
client_item(see below)
typedef struct client_item {
  union {
    SLIST_ENTRY( client_item ) free_node;
    RB_ENTRY( client_item )    active_node;
  };
  uint64_t                     ns;
  uint32_t                     cpu;
  rtems_record_event           event;
  uint64_t                     data;
  uint64_t                     counter;
} client_item;

to

typedef struct ctf_event {
  uint64_t                     ns;
  uint32_t                     cpu;
  rtems_record_event           event;
  uint64_t                     data;
  uint64_t                     counter;
} ctf_event;

I did that but rtems-tools build is failing because I think some part of
the codebase is dependent on
union {
    SLIST_ENTRY( client_item ) free_node;
    RB_ENTRY( client_item )    active_node;
  };

How should I deal with it?
-- 
*Ravindra Kumar Meena*,
B. Tech. Computer Science and Engineering,
Indian Institute of Technology (Indian School of Mines)
<https://www.iitism.ac.in/>, Dhanbad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20190620/9005f2f1/attachment-0002.html>


More information about the devel mailing list