Project

General

Profile

Bug #1125

pthread_rwlock_destroy() on locked rwlock return EBUSY

Added by Dmitry Moskalchuk about 4 years ago. Updated about 4 years ago.

Status:
Open
Priority:
Normal
Category:
libcrystax
Target version:
Start date:
11/09/2015
Due date:
% Done:

0%

Estimated time:
CPU Architecture:
Host OS:
Toolchain:
Android version:
CrystaX Version:

Description

There is no clear prohibition in POSIX specification for pthread_rwlock_destroy() to fail; however, EBUSY is not listed in the list of possible errors returned by pthread_rwlock_destroy(). Also, taking into account that on GNU/Linux with glibc pthread_rwlock_destroy() in the same case return 0, this behaviour looks wrong.

"Here":https://github.com/crystax/android-vendor-openpts/blob/master/conformance/interfaces/pthread_rwlock_wrlock/3-1.c is corresponding test case.

History

#1

Updated by Dmitry Moskalchuk about 4 years ago

  • Target version changed from 10.3.0 to 11.0.0

Also available in: Atom PDF