使用pthread的C語言中的讀取器/寫入器問題
[英]Reader/Writer problem in C using pthreads
問題描述
當我遇到C語言中的讀取器/寫入器問題時，我正在學習pthread。問題非常簡單，其中“寫入器”線程將從外部源訪問數據，而“讀取器”線程將從共享緩沖區讀取數據然后對數據進行偽處理。 讀取器和寫入器線程需要在while循環中連續運行。
我正在嘗試使用POSIX接口在標准的UNIX系統上實現和編譯此文件。
我已經看過一些堆棧溢出問題：
使用互斥和pthread的C語言中的Reader Writer程序
而我卻一無所獲。
這是我到目前為止的內容：
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>
#include <pthread.h>
#include <semaphore.h>
#include <assert.h>
#define BUFF_SIZE 50
#define M 10
#define N 20
int get_external_data(char *buffer, int bufferSizeInBytes);
void process_data(char *buffer, int bufferSizeInBytes);
int get_external_data(char *buffer, int bufferSizeInBytes){
int status;
int val;
char srcString[] = "0123456789abcdefghijklmnopqrstuvwxyxABCDEFGHIJKLMNOPQRSTUVWXYZ";
val = (int)(rand() % 62);
if (bufferSizeInBytes < val){
return (-1);
}
strncpy(buffer, srcString, val);
return val;
}
void process_data(char *buffer, int bufferSizeInBytes){
int i;
if(buffer) {
printf("thread %li - ", pthread_self());
for(i = 0; i < bufferSizeInBytes; i++) {
printf("%c", buffer[i]);
}
printf("\n");
memset(buffer, 0, bufferSizeInBytes);
} else {
printf("error in process data - %li\n", pthread_self());
}
return;
}
pthread_mutex_t data_lock = PTHREAD_MUTEX_INITIALIZER;
pthread_mutex_t print_lock = PTHREAD_MUTEX_INITIALIZER;
sem_t data_count;
typedef struct node {
struct node *next;
char *data;
int length;
} node_t;
node_t *head, *tail;
/**
* This thread is responsible for pulling data off of the shared data
* area and processing it using the process_data() API.
*/
void *reader_thread(void *arg) {
int rc;
node_t *removed_node;
while(1) {
rc = sem_wait(&data_count);
if (0 != rc) {
return NULL;
}
pthread_mutex_lock(&data_lock);
assert(NULL != head);
removed_node = head;
head = head->next;
pthread_mutex_unlock(&data_lock);
//Adding this lock for sake of readability at the cost of reduced consumption rate...will run out of memory eventually.
pthread_mutex_lock(&print_lock);
process_data(removed_node->data, removed_node->length);
pthread_mutex_unlock(&print_lock);
free(removed_node->data);
free(removed_node);
}
return NULL;
}
/**
* This thread is responsible for pulling data from a device using
* the get_external_data() API and placing it into a shared area
* for later processing by one of the reader threads.
*/
void *writer_thread(void *arg) {
int length;
char *buffer;
node_t *new_node;
new_node = (node_t*) malloc(sizeof(*new_node));
buffer = (char*) malloc(sizeof(*buffer) * BUFF_SIZE);
while(1) {
length = get_external_data(buffer, BUFF_SIZE);
if (length == -1) {
//data too big, discard it and try again;
continue;
}
new_node->next = NULL;
new_node->length = length;
new_node->data = buffer;
pthread_mutex_lock(&data_lock);
if (head == NULL) { //The linked list is completely empty
head = new_node;
tail = new_node;
} else { //There are items in the list and we're appending
tail->next = new_node;
tail = new_node;
}
pthread_mutex_unlock(&data_lock);
pthread_mutex_lock(&print_lock);
printf("thread %ld wrote - %s \n", pthread_self(), buffer);
pthread_mutex_unlock(&print_lock);
sem_post(&data_count);
buffer = (char*) malloc(sizeof(*buffer) * BUFF_SIZE);
new_node = (node_t*) malloc(sizeof(*new_node));
}
return NULL;
}
int main(int argc, char **argv) {
int i = sem_init(&data_count, 0, 0);
pthread_t dummy; //creating a dummy thread
for(i = 0; i < N; i++) {
pthread_create(&dummy, NULL, reader_thread, NULL);
}
for(i = 0; i < M; i++) {
pthread_create(&dummy, NULL, writer_thread, NULL);
}
sleep(100);
return 0;
}
那里有線程同步，沒有任何編譯錯誤，但是在編寫器線程在緩沖區上寫了幾次之后，我的程序停止了。
讀取器和寫入器線程需要在while循環中連續運行，但在我看來，它們不是必需的。
關於如何解決此問題的任何想法？
1 個解決方案
解決方案1
1 2019-04-17 15:50:37
使用gcc添加-lpthread選項以與pthread庫鏈接，我也鼓勵您添加-pedantic -Wextra -Wall選項
您的程序中有幾個問題，有些是編譯器指出的
在：
printf("thread %i - ", pthread_self()); printf("error in process data - %i\\n", pthread_self());
在POSIX標准中，不需要pthread_t是算術類型，因此它可以是struct等，並且不能將其寫為int 。 在您的情況下，它可能是一個int （很可能是unsigned long ），但這不是可移植的，因此最好自己管理與每個線程關聯的標識符。
在reader_thread ：
return;
但是函數返回一個void* ，用return NULL;代替return NULL; 例如
在writer_thread ：
printf("thread %d wrote - %s", buffer);
有三個問題：
- 類型為int的參數丟失（可能是您想要
pthread_self()） - 緩沖區是由
get_external_data使用strncpy設置的，因此不存在空結束符，但printf％s必需（當缺少的參數將被添加或％d被刪除時） - 緩沖區可以通過釋放
reader_thread，也許你認為它是由信號量保護，但這情況並非如此
在get_external_data 狀態未使用
在主要
usleep(100);
這是給線程工作的非常短的時間，實際上您只想被阻塞，因此可以將其替換為pthread_join(dummy, NULL);
有線程標識符的建議：在堆中分配一個int ，為它設置一個唯一的數字，然后將in參數提供給創建的線程：
int main() {
...
for(i = 0; i < N; i++) {
int * m = malloc(sizeof(int));
*m = i;
pthread_create(&dummy, NULL, reader_thread, m);
}
for(i = 0; i < M; i++) {
int * m = malloc(sizeof(int));
*m = 100 + i;
pthread_create(&dummy, NULL, writer_thread, m);
}
...
}
和
void *writer_thread(void *arg) {
int id = *((int*) arg);
...
free((int*) arg);
...
printf("thread %d wrote - %s", id, buffer);
...
}
和
void *reader_thread(void *arg) {
int id = *((int*) arg);
...
free((int*) arg);
...
process_data(removed_node->data, removed_node->length, id);
...
}
和
void process_data(char *buffer, int bufferSizeInBytes, int id){
...
printf("thread %i - ", id);
...
printf("error in process data - %i\n", id);
...
}
在上次更改之后，由於其他問題，在valgrind下執行的操作會出現錯誤：
pi@raspberrypi:/tmp $ gcc -g -pedantic -Wextra -Wall t.c -lpthread
pi@raspberrypi:/tmp $ valgrind ./a.out
==3847== Memcheck, a memory error detector
==3847== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==3847== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==3847== Command: ./a.out
==3847==
==3847== Thread 22:
==3847== Conditional jump or move depends on uninitialised value(s)
==3847== at 0x484B20C: strlen (vg_replace_strmem.c:458)
==3847== by 0x48FD68F: vfprintf (vfprintf.c:1637)
==3847== by 0x4902ADF: printf (printf.c:33)
==3847== by 0x10B83: writer_thread (t.c:144)
==3847== by 0x4898FC3: start_thread (pthread_create.c:458)
==3847== by 0x498D037: ??? (clone.S:76)
==3847==
thread 100 wrote - 0123456789abcdefghijklmnopqrstuvwxyxABCDEthread 103 wrote - 0123456789abcdefghijklmnopqrstuvwxyxthread 1 - 0123456789abcdefghijklmnopqrstuvwxyxABCDE
thread 0 - 0123456789abcdefghijklmnopqrstuvwxyx
thread 102 wrote - 0123456789abcdefghijklmnopqrstuvwxyxABthread 103 wrote - 0123456thread 2 - 012
thread 101 wrote - 0123456789abcdefghithread 105 wrote - 0123456789abcdefghijklmnopqrstuvwxyxABCDEFGHIJKLMthread 3 - 0123456
thread 109 wrote - 0123456789abcdefghijklmnopqrstuvwxyxAthread 3 - 0123456789abcdefghi
==3847== Invalid read of size 1
==3847== at 0x484B1EC: strlen (vg_replace_strmem.c:458)
==3847== by 0x48FD68F: vfprintf (vfprintf.c:1637)
==3847== by 0x4902ADF: printf (printf.c:33)
==3847== by 0x10B83: writer_thread (t.c:144)
==3847== by 0x4898FC3: start_thread (pthread_create.c:458)
==3847== by 0x498D037: ??? (clone.S:76)
==3847== Address 0x49fcd18 is 0 bytes inside a block of size 50 free'd
==3847== at 0x4848B8C: free (vg_replace_malloc.c:530)
==3847== Block was alloc'd at
==3847== at 0x4847568: malloc (vg_replace_malloc.c:299)
==3847==
thread 107 wrote - 0123456789abcdefgthread 100 wrote - thread 100 wrote - 0123456789athread 101 wrote - 0123456789abcthread 7 - 0123456789abcdefghijklmnopqrstuvwxyxABCDEFGHIJKLM
thread 7 - 0123456789abcdefghijklmnopqrstuvwxyxAB
thread 9 - 0123456789abc
thread 9 - 0123456789abcdefghijklmnopqrstuvwxyxA
thread 108 wrote - 0123456789abcdefghijklmnopqrstuvwxyxABthread 105 wrote - 01thread 8 - 0123456789ab
thread 108 wrote - 0123456789abcdefghithread 12 - 0123
thread 103 wrote - 0123456789abcdefghijklmnopqrstuvwxyxABCDEFGthread 101 wrote - 0123456789abcdefghijklmnopqrstuvthread 103 wrote - 0123456789abcdefghijklmnopqrstuvwxyxABCDEFGthread 101 wrote - 0123456789abcdefghijklmnopqrstuvthread 14 - 0123456789a
thread 101 wrote - 0123456789abcdefghijklthread 101 wrote - 0123456789abcdefghijklmnopqrstuvwxyxthread 101 wrote - 0123456789abcdefghijklmnopqrstuvwxyxABCDEFGHthread 101 wrote - 0123456789abcdefghijklmnopqthread 101 wrote - 0123456789abcdefghijklmnopqrstuthread 101 wrote - 0123thread 102 wrote - thread 2 - 0123456789abcdefghijklmnopqrstuv
thread 2 - 0123456789abcdefghijklmnopqr
thread 2 - 0123456789abcdefghi
thread 2 - 0123456789abcdefghijklmnopqrstuvwxyxABCDEFG
thread 100 wrote - 0123456789abcthread 100 wrote - 0123456789abcdefghijklmnopqrstuvwxyxABCDEFGHIJKthread 4 - 0123456789abcdefghijkl
thread 109 wrote - thread 13 - 0123456789abcdefghijklmnopqrstuvwxyxAB
thread 108 wrote - 0123456789abcdefghijklmnopqrstuvwxyxABCDEFGHIthread 19 - 0123456789abc
thread 101 wrote - 0thread 18 - 01
thread 108 wrote - 0123456thread 108 wrote - 01thread 108 wrote - 0123456789abcdefghijthread 10 - 0123456789abcdefghijklmnopq
thread 8 - 0123456789abcdefghijklmnopqrstu
==3847== Thread 30:
==3847== Conditional jump or move depends on uninitialised value(s)
==3847== at 0x484B1F4: strlen (vg_replace_strmem.c:458)
==3847== by 0x48FD68F: vfprintf (vfprintf.c:1637)
==3847== by 0x4902ADF: printf (printf.c:33)
==3847== by 0x10B83: writer_thread (t.c:144)
==3847== by 0x4898FC3: start_thread (pthread_create.c:458)
==3847== by 0x498D037: ??? (clone.S:76)
==3847==
==3847== Conditional jump or move depends on uninitialised value(s)
==3847== at 0x48FBEEC: vfprintf (vfprintf.c:1637)
==3847== by 0x4902ADF: printf (printf.c:33)
==3847== by 0x10B83: writer_thread (t.c:144)
==3847== by 0x4898FC3: start_thread (pthread_create.c:458)
==3847== by 0x498D037: ??? (clone.S:76)
==3847==
==3847== Conditional jump or move depends on uninitialised value(s)
==3847== at 0x48FBF0C: vfprintf (vfprintf.c:1637)
==3847== by 0x4902ADF: printf (printf.c:33)
==3847== by 0x10B83: writer_thread (t.c:144)
==3847== by 0x4898FC3: start_thread (pthread_create.c:458)
==3847== by 0x498D037: ??? (clone.S:76)
==3847==
==3847== Conditional jump or move depends on uninitialised value(s)
==3847== at 0x49245B8: _IO_file_xsputn@@GLIBC_2.4 (fileops.c:1294)
==3847== by 0x48FBF7B: vfprintf (vfprintf.c:1637)
==3847== by 0x4902ADF: printf (printf.c:33)
==3847== by 0x10B83: writer_thread (t.c:144)
==3847== by 0x4898FC3: start_thread (pthread_create.c:458)
==3847== by 0x498D037: ??? (clone.S:76)
==3847==
==3847== Conditional jump or move depends on uninitialised value(s)
==3847== at 0x48FBF80: vfprintf (vfprintf.c:1637)
==3847== by 0x4902ADF: printf (printf.c:33)
==3847== by 0x10B83: writer_thread (t.c:144)
==3847== by 0x4898FC3: start_thread (pthread_create.c:458)
==3847== by 0x498D037: ??? (clone.S:76)
==3847==
==3847== Conditional jump or move depends on uninitialised value(s)
==3847== at 0x48FBF90: vfprintf (vfprintf.c:1637)
==3847== by 0x4902ADF: printf (printf.c:33)
==3847== by 0x10B83: writer_thread (t.c:144)
==3847== by 0x4898FC3: start_thread (pthread_create.c:458)
==3847== by 0x498D037: ??? (clone.S:76)
==3847==
==3847== Conditional jump or move depends on uninitialised value(s)
==3847== at 0x48FBE24: vfprintf (vfprintf.c:1668)
==3847== by 0x4902ADF: printf (printf.c:33)
==3847== by 0x10B83: writer_thread (t.c:144)
==3847== by 0x4898FC3: start_thread (pthread_create.c:458)
==3847== by 0x498D037: ??? (clone.S:76)
==3847==
==3847== Conditional jump or move depends on uninitialised value(s)
==3847== at 0x48FBE6C: vfprintf (vfprintf.c:1668)
==3847== by 0x4902ADF: printf (printf.c:33)
==3847== by 0x10B83: writer_thread (t.c:144)
==3847== by 0x4898FC3: start_thread (pthread_create.c:458)
==3847== by 0x498D037: ??? (clone.S:76)
==3847==
thread 108 wrote - thread 108 wrote - 0123456789abcdefghijkthread 12 - 0123456789abcdefghijklmnopqrstuvwxyxABCDEFGHIJKL
thread 108 wrote - 0123456789abcdefghijthread 106 wrote - thread 5 - 0123456789abcdefg
thread 106 wrote - thread 106 wrote - 0123456789abcdefghijklmnopqrstuvwxyxABCDthread 16 - 0123456789abcdefghijklmnopqrstuvwx
thread 16 - 0123456789abcdefghijklmnopqrstuv
==3847==
==3847== HEAP SUMMARY:
==3847== in use at exit: 5,444 bytes in 74 blocks
==3847== total heap usage: 155 allocs, 81 frees, 8,138 bytes allocated
==3847==
==3847== LEAK SUMMARY:
==3847== definitely lost: 0 bytes in 0 blocks
==3847== indirectly lost: 0 bytes in 0 blocks
==3847== possibly lost: 4,080 bytes in 30 blocks
==3847== still reachable: 1,364 bytes in 44 blocks
==3847== suppressed: 0 bytes in 0 blocks
==3847== Rerun with --leak-check=full to see details of leaked memory
==3847==
==3847== For counts of detected and suppressed errors, rerun with: -v
==3847== Use --track-origins=yes to see where uninitialised values come from
==3847== ERROR SUMMARY: 51 errors from 10 contexts (suppressed: 6 from 3)
使用C中posix信號量的讀寫器應用中的分段錯誤
[英]Segmentation fault in reader-writer appilication using posix semaphore in c
聲明:本站的技術帖子網頁，遵循CC BY-SA 4.0協議，如果您需要轉載，請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.