Sponsored Content
Full Discussion: __throw
Top Forums Programming __throw Post 302231558 by lagigliaivan on Tuesday 2nd of September 2008 03:15:08 PM
Old 09-02-2008
__throw

Hi All,

We are fixing an application, and to do this we've used GDB.
We have a coredump file, therefore we can print a backtrace and watch the variables content at the moment of the crash.

This is the outcome of bt gd command:

0 0x0ffab7dc in __pthread_rwlock_unlock (rwlock=0x109db640) at ../nptl/sysdeps/pthread/pthread_rwlock_unlock.c:30
#1 0x1047a3a0 in m_rcv (unit=0, pkt=0x109dccfc, cookie=0x1090ffc8)
at net.c:284
#2 0x103c1640 in packet (unit=0, pkt=0x109dccfc) at packet.c:2505

In the line 30 of the file pthread_rwlock_unlock.c there is a calling to pthread_rwlock_unlock() function, but gdb shows __pthread_rwlock_unlock.

After realizing this, we looked for the definition of pthread_rwlock_unlock and we found the following:

extern int pthread_rwlock_unlock (pthread_rwlock_t *__rwlock) __THROW;

Somebody knows what is the meaning of __THROW???

Thanks !!!!!

P.D. We are using gcc and Linux
 
PTHREAD_RWLOCK_RDLOCK(3)				   BSD Library Functions Manual 				  PTHREAD_RWLOCK_RDLOCK(3)

NAME
pthread_rwlock_rdlock, pthread_rwlock_tryrdlock -- acquire a read/write lock for reading SYNOPSIS
#include <pthread.h> int pthread_rwlock_rdlock(pthread_rwlock_t *rwlock); int pthread_rwlock_tryrdlock(pthread_rwlock_t *rwlock); DESCRIPTION
The pthread_rwlock_rdlock() function acquires a read lock on rwlock, provided that rwlock is not presently held for writing and no writer threads are presently blocked on the lock. If the read lock cannot be immediately acquired, the calling thread blocks until it can acquire the lock. The pthread_rwlock_tryrdlock() function performs the same action, but does not block if the lock cannot be immediately obtained (i.e., the lock is held for writing or there are waiting writers). A thread may hold multiple concurrent read locks. If so, pthread_rwlock_unlock() must be called once for each lock obtained. The results of acquiring a read lock while the calling thread holds a write lock are undefined. IMPLEMENTATION NOTES
To prevent writer starvation, writers are favored over readers. RETURN VALUES
If successful, the pthread_rwlock_rdlock() and pthread_rwlock_tryrdlock() functions will return zero. Otherwise, an error number will be returned to indicate the error. SEE ALSO
pthread_rwlock_init(3), pthread_rwlock_trywrlock(3), pthread_rwlock_unlock(3), pthread_rwlock_wrlock(3) STANDARDS
The pthread_rwlock_rdlock() and pthread_rwlock_tryrdlock() functions are expected to conform to Version 2 of the Single UNIX Specification (``SUSv2''). ERRORS
The pthread_rwlock_tryrdlock() function will fail if: [EBUSY] The lock could not be acquired, because a writer holds the lock or was blocked on it. The pthread_rwlock_rdlock() and pthread_rwlock_tryrdlock() functions may fail if: [EAGAIN] The lock could not be acquired, because the maximum number of read locks against lock has been exceeded. [EDEADLK] The current thread already owns rwlock for writing. [EINVAL] The value specified by rwlock is invalid. [ENOMEM] Insufficient memory exists to initialize the lock (applies to statically initialized locks only). HISTORY
The pthread_rwlock_rdlock() function first appeared in FreeBSD 3.0. BSD
August 4, 1998 BSD
All times are GMT -4. The time now is 02:22 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy