Hello, For my GSoC project, user-configurable thread stack protection, I need to track, allocate, and manipulate attributes of shared as well as protected stacks. Dr.Gedare suggested that tracking them with score objects would be a good idea. He also indicated a good place to start and understand score objects would be through this ticket. <https://devel.rtems.org/ticket/3131>
>From the information that I could find in docs, my understanding of score objects is that they are a type of directive that helps introduce modularity to RTEMS as various types of RTEMS objects like message queues, semaphores, etc. can use the same set of directives for allocation/deallocation and control of their object types. Some of the examples of the implementation that I could find used _Object_Iniitialize_information() to initialize the object type, then _Object_Allocate()/Free() allocate/de-allocate the object. Object_Id is used to control the object type. My confusion is, how do we use object IDs to refer to and control the allocated objects? I also have some confusion in the above-mentioned ticket, it says- 'The mmap_h handler should construct a mapping object. A destructor is currently missing. Maybe the mmap_h handler should use a flag to deal with construction and destruction.' I am unclear as to how the mmap_h handler should precisely look like and where should it be defined? I would be grateful if you can provide some help in figuring this out. Regards, Utkarsh
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
