cvs commit: projects/validate/testcases/open_posix_testsuite/conformance/interfaces/pthread_mutex_timedlock 5-1.c 5-2.c 5-3.c

Mike Makonnen <[email protected]>
Newsgroups gmane.os.freebsd.devel.cvs.projects
Message-ID <200312311554.hBVFsmTp022013__3064.43996164507$1072886146@repoman.freebsd.org>
mtm         2003/12/31 07:54:48 PST

  FreeBSD projects repository

  Modified files:
    validate/testcases/open_posix_testsuite/conformance/interfaces/pthread_mutex_timedlock 
                                                                                           5-1.c 
                                                                                           5-2.c 
                                                                                           5-3.c 
  Log:
  Correct incorrect assertion about the behaviour of pthread_mutex_timedlock()
          o If the thread has the mutex already locked it will not block. It
            will return EDEADLK. Therefore, according to the standard,
            returning EINVAL if the timeout is invalid does not apply to
            such a thread.
  
  Better explanation for the case testing for immediate return
  with ETIMEDOUT when the timeout is set to the current time.
  
  Revision  Changes    Path
  1.2       +25 -25    projects/validate/testcases/open_posix_testsuite/conformance/interfaces/pthread_mutex_timedlock/5-1.c
  1.2       +25 -26    projects/validate/testcases/open_posix_testsuite/conformance/interfaces/pthread_mutex_timedlock/5-2.c
  1.2       +4 -5      projects/validate/testcases/open_posix_testsuite/conformance/interfaces/pthread_mutex_timedlock/5-3.c
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-projects
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.