EDIT3:每次需要时它会在一个新线程中生成,“input”是一个char *的副本,它在其中被释放。假设cURL函数是线程安全的。
EDIT4:假设任何不可见的函数都是线程安全的。
static void *Com_GoogleTranslate(void* input) {
CURL *easy_handle;
char *pos1, *pos2, url[1024], final[1024], inlang[8], outlang[8], *encoded;
const int const_strlen = strlen("\"translatedText\":\"");
struct GoogleMem chunk;
pthread_mutex_lock( &GoogleMessage_mutex );
// 'auto' is really empty in google API:
if (!strcmp(clu.translateIn->string, "auto"))
strcpy(inlang, "");
else
strcpy(inlang, clu.translateIn->string);
if (!strcmp(clu.translateOut->string, "auto"))
strcpy(outlang, "");
else
strcpy(outlang, clu.translateOut->string);
pthread_mutex_unlock( &GoogleMessage_mutex );
// Build the URL
url[0] = '\0';
strcat(url, "http://ajax.googleapis.com/ajax/services/language/translate?v=1.0&q=");
// Encode input into URL formatting
encoded = url_encode((char*)input);
if (!encoded) return 0;
strcat(url, encoded);
strcat(url, "&langpair=");
strcat(url, inlang);
strcat(url, "|");
strcat(url, outlang);
chunk.memory = malloc(1); // realloc grows it at Com_GoogleTranslateMem()
if (!chunk.memory) return 0;
chunk.size = 0; // no data yet
// cURL initialization for this sub-session:
easy_handle = qcurl_easy_init();
// ioq3-urt: was needed on https:// (v2 API) attempts when using GnuTLS
//qcurl_easy_setopt(curl_handle, CURLOPT_SSLVERSION, 3);
// set URL:
qcurl_easy_setopt(easy_handle, CURLOPT_URL, url);
// ioq3-urt: required for multithreading according to cURL doc.
qcurl_easy_setopt(easy_handle, CURLOPT_NOSIGNAL, 1);
// ioq3-urt: skip peer verification; required for google translate when SSL was used
//qcurl_easy_setopt(curl_handle, CURLOPT_SSL_VERIFYPEER, 0L);
// send all data to this function
qcurl_easy_setopt(easy_handle, CURLOPT_WRITEFUNCTION, Com_GoogleTranslateMem);
// we pass our 'chunk' struct to the callback function:
qcurl_easy_setopt(easy_handle, CURLOPT_WRITEDATA, (void *)&chunk);
// some servers don't like requests that are made without a user-agent field, so we provide one:
qcurl_easy_setopt(easy_handle, CURLOPT_USERAGENT, "libcurl-agent/1.0");
// ioq3-urt: Required by Google Translate terms:
qcurl_easy_setopt(easy_handle, CURLOPT_REFERER, "ioq3-urt");
// fetch it
qcurl_easy_perform(easy_handle);
// cleanup curl stuff
qcurl_easy_cleanup(easy_handle);
/*
Now chunk.memory points to a memory block that is chunk.size
bytes big and contains the remote file.
Nothing has yet deallocated that data, hence free() is used at the end.
*/
if (!chunk.size) {
pthread_mutex_lock( &GoogleMessage_mutex );
sprintf(GoogleMessage.message, "Translation: no data received from Google\n");
GoogleMessage.new_message = qtrue;
pthread_mutex_unlock( &GoogleMessage_mutex );
// Free up memory (same with the end)
if(chunk.memory) free(chunk.memory);
free(encoded);
free(input);
return 0;
}
if ( ( pos1 = strstr(chunk.memory, "\"translatedText\":\"") ) ) { // Make sure we use a valid file:
pos2 = strstr(pos1 + const_strlen, "\""); // position translated text ends
// Build the translated text:
final[0] = '\0';
strncat(final, pos1 + const_strlen, strlen(pos1) - ( strlen(pos2) + const_strlen ) );
// Final printing of the translated text:
pthread_mutex_lock( &GoogleMessage_mutex );
sprintf(GoogleMessage.message, "^2Translated^7: ^3%s\n", final);
GoogleMessage.new_message = qtrue;
pthread_mutex_unlock( &GoogleMessage_mutex );
#ifdef BUILD_FREETYPE
TTF_Find_Slot(final, clu.TTF_MessageMaxTime->integer);
#endif
} else {
pthread_mutex_lock( &GoogleMessage_mutex );
sprintf(GoogleMessage.message, "Translation: no valid translation file received from Google\n");
GoogleMessage.new_message = qtrue;
pthread_mutex_unlock( &GoogleMessage_mutex );
}
// Free allocated memory
if(chunk.memory) free(chunk.memory);
free(encoded);
free(input);
return 0;
}
我只在某些系统上遇到不稳定的行为,而我怀疑其硬件有问题(英特尔OpenGL?),我想知道是否遗漏了什么。
编辑:假设cURL本身就是线程安全的。
EDIT2:“input”是一个新的副本,它被释放到这个帖子中。
答案 0 :(得分:1)
只要在互斥锁保护部分之外调用的所有函数本身都是线程安全的,它看起来对我来说是安全的。
然而,有一个关于malloc的线程安全性的问题。请参阅this question。
答案 1 :(得分:1)
这不是线程安全问题,但有一点可以解决潜在问题。以下代码行未检查是否成功搜索:
pos2 = strstr(pos1 + const_strlen, "\""); // position translated text ends
如果chunk.memory
值在"translatedText":"
值之后没有包含另一个双引号,那么它将为null并且strlen()
内该值上的后续strncat
将为assert
可能导致访问冲突。
至少,在那里添加{{1}}以确认它确实总是成功可能没什么坏处。但我不知道其他功能在做什么。如果他们保证双引号在字符串中,那么这不是问题。
此外,从“我对所涉及的数据一无所知”问题是关于字符串长度的盲假设都适合1024个缓冲区。从防御性编码的角度来看,对这些呼叫的额外检查可能不会受到伤害。
否则,我同意(+)与JeremyP根据给定的代码看起来是线程安全的。