pthreads

问题 I was playing with std::thread and I was wondering how is it possible to get the thread id of a new std::thread() , I am not talking about std::thread::id but rather the OS Id given to the thread ( you can view it using pstree ). This is only for my knowledge, and it's targeted only to Linux platforms (no need to be portable). I can get the Linux Thread Id within the thread like this : #include <iostream> #include <thread> #include <unistd.h> #include <sys/syscall.h> #include <sys/types.h>

问题 I was playing with std::thread and I was wondering how is it possible to get the thread id of a new std::thread() , I am not talking about std::thread::id but rather the OS Id given to the thread ( you can view it using pstree ). This is only for my knowledge, and it's targeted only to Linux platforms (no need to be portable). I can get the Linux Thread Id within the thread like this : #include <iostream> #include <thread> #include <unistd.h> #include <sys/syscall.h> #include <sys/types.h>

问题 My env is Windows8.1 (64bit) and using Visual Studio 2010. I did put all *.dll files in system32 , SYSWOW64(because I use win8 64bit.) and link location where *.lib file for x64-system with VC 2010. of course, I add additional folder lib forders.. , include folders.. etc.. but when I try compile "pthread-used" project, fatal error has occur. -source #include<pthread.h> #include<stdio.h> int doit_id,trd_id; pthread_t trd; void *doit(void *data){ doit_id = (int)data; return 0; } int main(){ trd

问题 As it is said that Mutex are needed to protect the Condition Variables. Is the reference here to the actual condition variable declared as pthread_cond_t OR A normal shared variable count whose values decide the signaling and wait. ? 回答1: is the reference here to the actual condition variable declared as pthread_cond_t or a normal shared variable count whose values decide the signaling and wait? The reference is to both. The mutex makes it so that the shared variable ( count in your question)

问题 I read the Linux man page and OpenGroup for pthread_mutex_lock and get this: If successful, the pthread_mutex_lock() and pthread_mutex_unlock() functions shall return zero, otherwise, an error number shall be returned to indicate the error. The pthread_mutex_trylock() function shall return zero if a lock on the mutex object referenced by mutex is acquired. Otherwise, an error number is returned to indicate the error. I was confused by these two lines. If you both return zero when sucess and

问题 I read the Linux man page and OpenGroup for pthread_mutex_lock and get this: If successful, the pthread_mutex_lock() and pthread_mutex_unlock() functions shall return zero, otherwise, an error number shall be returned to indicate the error. The pthread_mutex_trylock() function shall return zero if a lock on the mutex object referenced by mutex is acquired. Otherwise, an error number is returned to indicate the error. I was confused by these two lines. If you both return zero when sucess and

问题 I can see number of threads used in application by going to /proc/$(pidof task)/ and giving cat status. Is there any way to check individual thread priority in linux using commands? Regards, Learner 回答1: Run ps with -m -l . It will list all the thread and priority with respect to particular PID ps -m -l [PID] Example: PC@PCuser:~$ ps -m -l 10070 F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD 0 - 1000 10070 1 0 - - - 31325 - ? 0:42 gedit 0 S 1000 - - 0 80 0 - - poll_s - 0:41 - 1 S 1000 -

问题 GDB normally stops all threads if a breakpoint is reached (or Ctrl+C is pressed in the GDB shell). I'm aware that commands like scheduler-locking and schedule-multiple exists, but I see no possibility to let a defined thread run in the background while another is debugged. 回答1: You can use set target-async on to enable asynchronous mode, if your target supports it. Then, you can specify background execution with commands. For example, continue& can be used to run a single thread, and

问题 How exactly i can destroy a pthread mutex variable ? Here is what i want to do. I want to have objects (structure variables) cached , which are looked up by key. I want to have minimum granularity of locks here. So i want to have a lock for each object probably embedded in the structure so that i can have object level locking. Now the problem is how to safely destroy these objects ? Looks like first step is to remove the object from the lookup table so that the object is not accessible in

问题 I'm having some trouble in my first foray into threads in C. I'm trying (for now) to write a very simple server program that accepts a socket connection and starts a new thread to process it. It seems to work fine except that it will only create about 300 threads (303, sometimes 304) before pthread_create() fails with the EAGAIN code, which means: "The system lacked the necessary resources to create another thread, or the system-imposed limit on the total number of threads in a process