GTK bug? xcb_io.c: 140

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat GTK bug? xcb_io.c: 140
# 8  
Old 03-21-2014
You should always use a mutex for global variables when dealing with multiple threads. This is particularly important on multicore systems -- the mutex doesn't just prevent race conditions, it forces two cores to sync their memory (one core could change the memory, and the other core might not know, old memory in cache, until the mutex forces it to sync).
Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Use stty columns 140 in .profile on ksh

Hi, I am trying to put stty columns 140 in .profile to set column width to 140 so I don't have to manully do it every time. My main goal is to avoid seeing "Terminal too wide" message whenever I try to use vi editor in full screen. I am on korn shell echo $SHELL /bin/ksh So even... (8 Replies)
Discussion started by: pat_pramod
8 Replies

2. Programming

curses.h not found , gtk/gtk.h not found

i have downloaded <libncurses5-dev_5.7+20101128-1_i386.deb> and <ndk++-0.0.1alpha4.tar.bz2> which contains the header files curses.h and gtk/gtk.h .. i have also included them using .. #include "/home/ball/Desktop/Sudoku/project/libncurses5-dev_5.7+20101128-1_i386/usr/include/curses.h" ... (2 Replies)
Discussion started by: upvan111
2 Replies

3. UNIX for Dummies Questions & Answers

FTP: Error -140: remote mkdir failed

I've just installed vsftpd on Ubuntu 9.04 server. I can access using my ftp client, however I cannot use mkdir either upload files. I get the following errors: `Error -140: remote mkdir failed` My configuration file has: write_enable = YES Is there some other parameter I should... (2 Replies)
Discussion started by: aneuryzma
2 Replies

4. AIX

Root password for fresh 5.1 install on 43p-140?

I've installed AIX 5.1 on a 43p-140, but am unable to log in. At no point in the install did it ask me for a root password. When it boots to the console prompt, I enter "root" as a username, and then after 1 second it cycles right back to another root prompt. I am accessing the 43p-140... (4 Replies)
Discussion started by: akbar
4 Replies
Login or Register to Ask a Question
tis_mutex_init(3)					     Library Functions Manual						 tis_mutex_init(3)

NAME
tis_mutex_init - Initializes a mutex object. LIBRARY
Standard C Library (libc.so, libc.a) SYNOPSIS
#include <tis.h> int tis_mutex_init( pthread_mutex_t *mutex); STANDARDS
None PARAMETERS
Pointer to a mutex object (passed by reference) to be initialized. DESCRIPTION
This routine initializes a mutex object with the DECthreads default mutex attributes. A mutex is a synchronization object that allows mul- tiple threads to serialize their access to shared data. The mutex is initialized and set to an unlocked state. Your program can use the PTHREAD_MUTEX_INITIALIZER macro to statically initialize a mutex object without calling this routine. Static ini- tialization can be used only for a condition variable with class extern or static - automatic (stack local) objects must be initialized by calling tis_mutex_init(3). Use this macro as follows: pthread_mutex_t mutex = PTHREAD_MUTEX_INITIALIZER RETURN VALUES
If an error condition occurs, this routine returns an integer value indicating the type of error, the mutex is not initialized, and the contents of mutex are undefined. Possible return values are as follows: Successful completion. The system lacks the necessary resources to initialize a mutex. The implementation has detected an attempt to reinitialize mutex (a previously initialized, but not yet destroyed mutex). The value specified by mutex is not a valid mutex. Insufficient memory exists to initialize the mutex. The caller does not have privileges to perform this operation. ERRORS
None RELATED INFORMATION
Functions: tis_mutex_destroy(3), tis_mutex_lock(3), tis_mutex_trylock(3), tis_mutex_unlock(3) Manuals: Guide to DECthreads and Programmer's Guide delim off tis_mutex_init(3)