[RTEMS Project] #4844: Unchecked boundaries

[RTEMS trac]

#4844: Unchecked boundaries
---------------------------+---------------------
 Reporter:  Daniel Páscoa  |       Owner:  (none)
     Type:  defect         |      Status:  new
 Priority:  normal         |   Milestone:
Component:  admin          |     Version:  6
 Severity:  normal         |  Resolution:
 Keywords:  qualification  |  Blocked By:
 Blocking:                 |
---------------------------+---------------------

Comment (by Sebastian Huber):

 These should have been three tickets and not just one.

 1. The message send directives use the size as an output only parameter.
 If you change this to an input and output parameter, then you may break
 existing applications which do not set the size parameter to a proper
 value.

 2. The Semaphore Control Block size is defined by the application
 configuration:

 {{{#!c
 #if CONFIGURE_MAXIMUM_SEMAPHORES > 0
   SEMAPHORE_INFORMATION_DEFINE(
     CONFIGURE_MAXIMUM_SEMAPHORES,
     _CONFIGURE_SCHEDULER_COUNT
   );
 #endif
 }}}

 3. There are lots of other values in the Thread Control Block which have
 to be correct. Why should we add a check here specifically? We could add
 an _Assert().

--
Ticket URL: <http://devel.rtems.org/ticket/4844#comment:1>
RTEMS Project <http://www.rtems.org/>
RTEMS Project