GTK bug? xcb_io.c: 140

Operating Systems Linux Red Hat GTK bug? xcb_io.c: 140

03-21-2014

Registered User

23,310, 4,623

Join Date: Aug 2005

Last Activity: 7 July 2020, 11:47 AM EDT

Location: Saskatchewan

Posts: 23,310

Thanks Given: 1,331

Thanked 4,623 Times in 4,217 Posts

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).

Corona688

View Public Profile for Corona688

Visit Corona688's homepage!

Find all posts by Corona688

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...

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" ...

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...

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...

LEARN ABOUT SUNOS

_lwp_mutex_lock

_lwp_mutex_lock(2)						   System Calls 						_lwp_mutex_lock(2)

NAME

       _lwp_mutex_lock, _lwp_mutex_unlock, _lwp_mutex_trylock - mutual exclusion

SYNOPSIS

       #include <sys/lwp.h>

       int _lwp_mutex_lock(lwp_mutex_t *mp);

       int _lwp_mutex_trylock(lwp_mutex_t *mp);

       int _lwp_mutex_unlock(lwp_mutex_t *mp);

DESCRIPTION

       These  functions  serialize the execution of lightweight processes. They are useful for ensuring that only one lightweight process can exe-
       cute a critical section of code at any one time (mutual exclusion).  LWP mutexes must be initialized to 0 before use.

       The _lwp_mutex_lock() function locks the LWP mutex pointed to by mp. If the mutex is already locked, the calling LWP blocks until the mutex
       becomes available.  When _lwp_mutex_lock() returns, the mutex is locked and the calling LWP is the "owner".

       The  _lwp_mutex_trylock()  function  attempts  to  lock the mutex. If the mutex is already locked it returns with an error. If the mutex is
       unlocked, it is locked and _lwp_mutex_trylock() returns.

       The _lwp_mutex_unlock() function unlocks a locked mutex. The mutex must be locked and the calling LWP must be the one that last locked  the
       mutex (the owner). If any other LWPs are waiting for the mutex to become available, one of them is unblocked.

RETURN VALUES

       Upon successful completion, 0 is returned. A non-zero value indicates an error.

ERRORS

       If  any of the following conditions are detected, _lwp_mutex_lock(), _lwp_mutex_trylock(), and _lwp_mutex_unlock() fail and return the cor-
       responding value:

       EINVAL	       The mp argument points to an invalid LWP mutex.

       EFAULT	       The mp argument points to an illegal address.

       If any of the following conditions occur, _lwp_mutex_trylock() fails and returns the corresponding value:

       EBUSY	       The mp argument points to a locked mutex.

SEE ALSO

       intro(2), _lwp_cond_wait(2)

SunOS 5.10							    30 Jul 1992 						_lwp_mutex_lock(2)

Red Hat