2012 年 4 月 10 日更新: 由 libc 补丁修复
我在取消线程时遇到问题,这些线程使用带有属性集pthread_cond_wait
的互斥锁。PTHREAD_PRIO_INHERIT
不过,这只发生在某些平台上。
以下最小示例演示了这一点:(编译g++ <filename>.cpp -lpthread
)
#include <pthread.h>
#include <iostream>
pthread_mutex_t mutex;
pthread_cond_t cond;
void clean(void *arg) {
std::cout << "clean: Unlocking mutex..." << std::endl;
pthread_mutex_unlock((pthread_mutex_t*)arg);
std::cout << "clean: Mutex unlocked..." << std::endl;
}
void *threadFunc(void *arg) {
int ret = 0;
pthread_mutexattr_t mutexAttr;
ret = pthread_mutexattr_init(&mutexAttr); std::cout << "ret = " << ret << std::endl;
//Comment out the following line, and everything works
ret = pthread_mutexattr_setprotocol(&mutexAttr, PTHREAD_PRIO_INHERIT); std::cout << "ret = " << ret << std::endl;
ret = pthread_mutex_init(&mutex, &mutexAttr); std::cout << "ret = " << ret << std::endl;
ret = pthread_cond_init(&cond, 0); std::cout << "ret = " << ret << std::endl;
std::cout << "threadFunc: Init done, entering wait..." << std::endl;
pthread_cleanup_push(clean, (void *) &mutex);
ret = pthread_mutex_lock(&mutex); std::cout << "ret = " << ret << std::endl;
while(1) {
ret = pthread_cond_wait(&cond, &mutex); std::cout << "ret = " << ret << std::endl;
}
pthread_cleanup_pop(1);
return 0;
}
int main() {
pthread_t thread;
int ret = 0;
ret = pthread_create(&thread, 0, threadFunc, 0); std::cout << "ret = " << ret << std::endl;
std::cout << "main: Thread created, waiting a bit..." << std::endl;
sleep(2);
std::cout << "main: Cancelling threadFunc..." << std::endl;
ret = pthread_cancel(thread); std::cout << "ret = " << ret << std::endl;
std::cout << "main: Joining threadFunc..." << std::endl;
ret = pthread_join(thread, NULL); std::cout << "ret = " << ret << std::endl;
std::cout << "main: Joined threadFunc, done!" << std::endl;
return 0;
}
每次我运行它时,都会main()
挂起pthread_join()
。gdb 回溯显示以下内容:
Thread 2 (Thread 0xb7d15b70 (LWP 257)):
#0 0xb7fde430 in __kernel_vsyscall ()
#1 0xb7fcf362 in __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/lowlevellock.S:142
#2 0xb7fcc9f9 in __condvar_w_cleanup () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:434
#3 0x08048fbe in threadFunc (arg=0x0) at /home/pthread_cond_wait.cpp:22
#4 0xb7fc8ca0 in start_thread (arg=0xb7d15b70) at pthread_create.c:301
#5 0xb7de73ae in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130
Thread 1 (Thread 0xb7d166d0 (LWP 254)):
#0 0xb7fde430 in __kernel_vsyscall ()
#1 0xb7fc9d64 in pthread_join (threadid=3083950960, thread_return=0x0) at pthread_join.c:89
#2 0x0804914a in main () at /home/pthread_cond_wait.cpp:41
如果PTHREAD_PRIO_INHERIT
未在互斥锁上设置,则一切正常,并且程序干净地退出。
有问题的平台:
- 嵌入式 AMD Fusion 板,运行基于PTXDist的 32 位 Linux 3.2.9-rt16(带有RTpatch 16)。我们正在使用最新的OSELAS i686 交叉工具链 (2011.11.1),使用 gcc 4.6.2、glibc 2.14.1、binutils 2.21.1a、内核 2.6.39。
- 与 2011.03.1 工具链相同的板(gcc 4.5.2 / glibc 2.13 / binutils 2.18 / kernel 2.6.36)。
没有问题的平台:
- 我们自己的 ARM 板,也运行 PTXDist Linux(32 位 2.6.29.6-rt23),使用 OSELAS arm-v4t 交叉工具链(1.99.3)和 gcc 4.3.2 / glibc 2.8 / binutils 2.18 / kernel 2.6.27 .
- 我的笔记本电脑(英特尔酷睿 i7),运行 64 位 Ubuntu 11.04(虚拟化/内核 2.6.38.15-generic),gcc 4.5.2 / eglibc 2.13-0ubuntu13.1 / binutils 2.21.0.20110327。
我一直在网上寻找解决方案,并且遇到了一些我尝试过的补丁,但没有任何效果:
我们是在代码中做错了什么,恰好在某些平台上工作,还是这是底层系统中的错误?如果有人知道去哪里看,或者知道任何补丁或类似的尝试,我很乐意听到。
谢谢!
更新: