[RTEMS Project] #3975: RTEMS 5 : sem_wait + sem_destroy behavior change

[RTEMS trac]

#3975: RTEMS 5 : sem_wait + sem_destroy behavior change
--------------------------+---------------------
 Reporter:  andrei.lupas  |       Owner:  (none)
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:
Component:  admin         |     Version:  5
 Severity:  normal        |  Resolution:
 Keywords:                |  Blocked By:
 Blocking:                |
--------------------------+---------------------

Comment (by andrei.lupas):

 Indeed, behavior is according to POSIX spec, but in the "undefined" area
 "The effect of destroying a semaphore upon which other threads are
 currently blocked is undefined."
 In this case, the "undefined" behavior changed from SUCCESS to
 error:EBUSY, and this impacts some existing apps.
 On short term, I suppose I need to move to classic API semaphores.
 Thanks a lot for the prompt feedback.
 Andrei.

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