[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Mutex error checking (was: [PULL 00/26] Migration pull
|
From: |
Peter Maydell |
|
Subject: |
Re: [Qemu-devel] Mutex error checking (was: [PULL 00/26] Migration pull request) |
|
Date: |
Thu, 2 Jul 2015 13:58:40 +0100 |
On 2 July 2015 at 13:55, Markus Armbruster <address@hidden> wrote:
> From pthread_mutexattr_settype(3p):
>
> PTHREAD_MUTEX_ERRORCHECK
>
> This type of mutex provides error checking. A thread
> attempting to relock this mutex without first unlocking it
> shall return with an error. A thread attempting to unlock
> a mutex which another thread has locked shall return with
> an error. A thread attempting to unlock an unlocked mutex
> shall return with an error.
>
> Not sure it detects this particular problem.
>
> Should we use it with --enable-debug or something?
It breaks when fork is involved, unfortunately:
https://lists.gnu.org/archive/html/qemu-devel/2015-06/msg06016.html
-- PMM
- [Qemu-devel] [PULL 22/26] migration: ensure we start in NONE state, (continued)
- [Qemu-devel] [PULL 22/26] migration: ensure we start in NONE state, Juan Quintela, 2015/07/01
- [Qemu-devel] [PULL 23/26] migration: Use always helper to set state, Juan Quintela, 2015/07/01
- [Qemu-devel] [PULL 25/26] migration: create migration event, Juan Quintela, 2015/07/01
- [Qemu-devel] [PULL 26/26] migration: Add migration events on target side, Juan Quintela, 2015/07/01
- [Qemu-devel] [PULL 24/26] migration: No need to call trace_migrate_set_state(), Juan Quintela, 2015/07/01
- Re: [Qemu-devel] [PULL 00/26] Migration pull request, Peter Maydell, 2015/07/02