diff options
| author | Richard Guenther <rguenther@suse.de> | 2012-03-12 14:23:27 +0000 |
|---|---|---|
| committer | Richard Biener <rguenth@gcc.gnu.org> | 2012-03-12 14:23:27 +0000 |
| commit | 33e3e24d74dd21373b4059738a04feda26312f1c (patch) | |
| tree | 0b5bc7d4e9657ab185aa593ffce407fded974b61 /libgcc/gthr.h | |
| parent | 24219d389088db7eb34f492e89643a5246ec12a5 (diff) | |
| download | gcc-33e3e24d74dd21373b4059738a04feda26312f1c.zip gcc-33e3e24d74dd21373b4059738a04feda26312f1c.tar.gz gcc-33e3e24d74dd21373b4059738a04feda26312f1c.tar.bz2 | |
re PR gcov-profile/49484 (gcov crash if two(or more) forks happen at the same time)
2012-03-12 Richard Guenther <rguenther@suse.de>
* gthr.h (__GTHREAD_MUTEX_INIT_FUNCTION): Adjust specification.
* gthr-posix.h (__GTHREAD_MUTEX_INIT_FUNCTION): Define.
(__gthread_mutex_init_function): New function.
* gthr-single.h (__GTHREAD_MUTEX_INIT_FUNCTION): Define.
PR gcov/49484
* libgcov.c: Include gthr.h.
(__gcov_flush_mx): New global variable.
(init_mx, init_mx_once): New functions.
(__gcov_flush): Protect self with a mutex.
(__gcov_fork): Re-initialize mutex after forking.
* unwind-dw2-fde.c: Change condition under which to use
__GTHREAD_MUTEX_INIT_FUNCTION.
From-SVN: r185231
Diffstat (limited to 'libgcc/gthr.h')
| -rw-r--r-- | libgcc/gthr.h | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/libgcc/gthr.h b/libgcc/gthr.h index 03a3ee1..813abe1 100644 --- a/libgcc/gthr.h +++ b/libgcc/gthr.h @@ -52,11 +52,12 @@ see the files COPYING3 and COPYING.RUNTIME respectively. If not, see to initialize __gthread_mutex_t to get a fast non-recursive mutex. __GTHREAD_MUTEX_INIT_FUNCTION - some systems can't initialize a mutex without a - function call. On such systems, define this to a - function which looks like this: + to initialize __gthread_mutex_t to get a fast + non-recursive mutex. + Define this to a function which looks like this: void __GTHREAD_MUTEX_INIT_FUNCTION (__gthread_mutex_t *) - Don't define __GTHREAD_MUTEX_INIT in this case + Some systems can't initialize a mutex without a + function call. Don't define __GTHREAD_MUTEX_INIT in this case. __GTHREAD_RECURSIVE_MUTEX_INIT __GTHREAD_RECURSIVE_MUTEX_INIT_FUNCTION as above, but for a recursive mutex. |