From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Programmingkid <programmingkidx@gmail.com>
Cc: qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Help with deadlock when using sound
Date: Wed, 13 May 2015 15:56:04 +0200 [thread overview]
Message-ID: <555357F4.7060005@redhat.com> (raw)
In-Reply-To: <CAFEAcA8XyjgpHz0i0nprHKkP2Genh=Z2+D7qAeOawrZzFSZzYg@mail.gmail.com>
On 13/05/2015 11:38, Peter Maydell wrote:
>
> then we'll turn on the error checking, and a double-unlock
> will result in a call to abort(). If you run QEMU under
> a debugger you'll get a backtrace which will tell you which
> code did the second unlock (and thus which mutex it is).
>
> (Linux has a similar attribute, though it is named
> PTHREAD_MUTEX_ERRORCHECK_NP; we might want to consider
> turning on mutex debugging for --enable-debug builds.)
We had it, but I had to disable it because it doesn't work (at all) when
you fork. The PID changes under the code's feet and subsequent unlocks
do not like it.
Paolo
next prev parent reply other threads:[~2015-05-13 13:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 16:40 [Qemu-devel] Help with deadlock when using sound Programmingkid
2015-05-06 17:00 ` Peter Maydell
2015-05-06 19:41 ` Programmingkid
2015-05-06 21:10 ` Peter Maydell
2015-05-06 21:19 ` Programmingkid
2015-05-06 21:31 ` Peter Maydell
2015-05-06 21:41 ` Programmingkid
2015-05-06 21:53 ` Peter Maydell
2015-05-06 21:30 ` Programmingkid
2015-05-10 14:54 ` Paolo Bonzini
2015-05-10 15:55 ` Paolo Bonzini
2015-05-10 19:41 ` Programmingkid
2015-05-11 22:43 ` Programmingkid
2015-05-12 7:45 ` Paolo Bonzini
2015-05-12 18:59 ` Programmingkid
2015-05-13 3:23 ` Programmingkid
2015-05-13 9:38 ` Peter Maydell
2015-05-13 13:54 ` Programmingkid
2015-05-13 15:03 ` Peter Maydell
2015-05-13 13:56 ` Paolo Bonzini [this message]
[not found] <BDB13C47-556C-4C58-8A4C-2BB7343F1FB4@gmail.com>
2015-05-10 14:05 ` Programmingkid
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=555357F4.7060005@redhat.com \
--to=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=programmingkidx@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).