search for: pthread_mutex

FreeBSD does not define pthread_mutexattr_setpshared: gmake[1]: Entering directory `/usr/home/jeffc/llvm/obj/lib/System' llvm[1]: Compiling Mutex.cpp for Release build /usr/home/jeffc/llvm/obj/../lib/System/Mutex.cpp:42: warning: the address of `int llvm::pthread_mutex_init(llvm::pthread_mutex**, llvm::pthread_mutex_attr* const*...

On Fri, Jun 6, 2014 at 10:57 PM, Kostya Serebryany <kcc at google.com> wrote: > As for the deadlocks, indeed it is possible to add deadlock detection > directly to std::mutex and std::spinlock code. > It may even end up being more efficient than a standalone deadlock > detector -- > but only if we can add an extra word to the mutex/spinlock object. > The deadlock

Commit d02d9c9d used pthread_mutex to avoid interleaving output. However, the standard provides flockfile() for grouping related FILE* I/O that must not be interleaved; and that may be lighter-weight than rolling our own locking. Signed-off-by: Eric Blake <eblake@redhat.com> --- Pushing this one; as a related conversation on...

I added LOG statements to mutex.c printing the strerror from the return values.   From   ret = pthread_mutexattr_init(&ma); in line 570   I got errorno 16 --> device busy.   But due the manual of pthread_mutex_attr_init() there should only be ENOMEM and EINVAL...   Doing gdb smbd -> run Doe not reveal anything, but I never used gdb for debugging anything. I just gave it a shot...         Gesend...

...encounter it on 4.9.5. > > I confirmed in 4.10.2, it happens: > > winbindd.log:  tdb(/tmw-nas-3p/samba/var/lock/gencache.tdb): tdb_open_ex: tdb_mutex_init failed for /tmw-nas-3p/samba/var/lock/gencache.tdb: Device busy > > So either apply OS fix, or apply a software fix (zeroing pthread_mutex_t before pthread_mutex_init()).   This all should be based on the following issue:   https://www.illumos.org/issues/9959   As far as I understand the issue making an software fix in samba for the OS seems more reasonable since the problem can occur sporadic and thus again... Could you tell me how t...

...reeBSD" llvm_cv_platform_type="Unix" ;; So I forged `freebsd' $ ./configure --build=i386-unknown-freebsd3.8 and ./configure completed successfully. gmake stopped with llvm[1]: Compiling Mutex.cpp for Debug build Mutex.cpp:55: warning: the address of `int pthread_mutex_init(volatile pthread_mutex**, pthread_mutex_attr* const*)', will always be `true' Mutex.cpp: In constructor `llvm::sys::Mutex::Mutex(bool)': Mutex.cpp:80: error: `pthread_mutexattr_setpshared' undeclared (first use this function) Mutex.cpp:80: error: (Each...

Hi, I am using XenServer5.6 FP1 GA release with openvswitch as network backend. When I create VM through xapi, "apache.xmlrpc.XmlRpcException: I/O error" happens very frequently. At meanwhile my xencenter lost connection to hosts. Another thing is when I tried to kill VMs from xencenter, it complains "Internal error:Sys_error("Thread.create: Cannot allocate

...rm_type="Unix" ;; > >So I forged `freebsd' > > $ ./configure --build=i386-unknown-freebsd3.8 > >and ./configure completed successfully. gmake stopped with > > llvm[1]: Compiling Mutex.cpp for Debug build > Mutex.cpp:55: warning: the address of `int pthread_mutex_init(volatile > pthread_mutex**, pthread_mutex_attr* const*)', will always be `true' > Mutex.cpp: In constructor `llvm::sys::Mutex::Mutex(bool)': > Mutex.cpp:80: error: `pthread_mutexattr_setpshared' undeclared (first use this > function) > Mutex....

...rm_type="Unix" ;; > >So I forged `freebsd' > > $ ./configure --build=i386-unknown-freebsd3.8 > >and ./configure completed successfully. gmake stopped with > > llvm[1]: Compiling Mutex.cpp for Debug build > Mutex.cpp:55: warning: the address of `int pthread_mutex_init(volatile > pthread_mutex**, pthread_mutex_attr* const*)', will always be `true' > Mutex.cpp: In constructor `llvm::sys::Mutex::Mutex(bool)': > Mutex.cpp:80: error: `pthread_mutexattr_setpshared' undeclared (first use this > function) > Mutex....

> > > On FreeBSD and OS X, the underlying pthread_mutex can already do deadlock > detection, so I don't see why you'd need to add another word. The > PTHREAD_MUTEX_ERRORCHECK attribute has been part of POSIX since 1997, so > I'd expect it to be supported everywhere. > PTHREAD_MUTEX_ERRORCHECK detects the deadlock that already h...

Hi Josephm > I would like to test but the I modigied the configure to make unknown > = OpenBSD and Unix and go pretty far but it died right after 'supports > mkdir' yes... Could that have been `checking for mkdir...'? > then the next line was 'your system is unsupported'' Have you looked at ./config.log. ./configure creates this as it runs as a trace of the

...; - Removing the close handler is not The Right Thing To Do. Rather, invoke the close handler where necessary. Unfortunately, memshr seems blatantly devoid of any cleanup handling. The problem seems much harder than what it''s worth solving here: exiting memshr clients need to not leave a pthread_mutex locked in a shared memory area (ugly, posix named semaphores exist for a reason!), need to agree that the last one out will destroy the mutex, need to clean up shared files, etc. Can we at least atexit shm_area_close? Andres > > shared_memshr_info_t * shm_shared_info_open(int unlink) >...

I would like to test but the I modigied the configure to make unknown = OpenBSD and Unix and go pretty far but it died right after 'supports mkdir' yes... then the next line was 'your system is unsupported'' I have gcc 3.3 on OpenBSD 3.3 pro-police stack compiler... I am only really interested in testing the C/C++ but C primarily for my work. regards, Joseph Altea

Hello LLVM Developers, Within Google, we have a growing range of needs that existing libc implementations don't quite address. This is pushing us to start working on a new libc implementation. Informal conversations with others within the LLVM community has told us that a libc in LLVM is actually a broader need, and we are increasingly consolidating our toolchains around LLVM. Hence, we