From: Gerd Hoffmann <kraxel@redhat.com>
To: Christophe de Dinechin <cdupontd@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: Understanding initialization order for spice in qemu
Date: Fri, 19 Jun 2020 09:57:06 +0200 [thread overview]
Message-ID: <20200619075706.ovi5cauic4zufewz@sirius.home.kraxel.org> (raw)
In-Reply-To: <1D26F746-92AA-4BA4-BF92-A498DA2C67C9@redhat.com>
On Thu, Jun 18, 2020 at 01:11:44PM +0200, Christophe de Dinechin wrote:
> Hi Gerd,
>
>
> When I build qemu on master with moduels enabled, and run with spice, I occasionally see:
>
> qemu-system-x86_64: util/module.c:136: module_load_file: Assertion `QTAILQ_EMPTY(&dso_init_list)' failed.
Never saw that one.
I've noticed though the qemu build system doesn't rebuild code on cflags
changes, and switching object files from -y to -m (which adds -fPIC to
cflags) can cause build errors which go away when you rm -rf the build
tree (or at least the subdirectory where I'm hacking on) and try again.
> Asking because I don't recall ever seeing that on a clean build.
Yea, that hints it is the same problem.
HTH,
Gerd
prev parent reply other threads:[~2020-06-19 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 11:11 Understanding initialization order for spice in qemu Christophe de Dinechin
2020-06-18 11:30 ` Alex Bennée
2020-06-19 7:57 ` Gerd Hoffmann [this message]
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=20200619075706.ovi5cauic4zufewz@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=cdupontd@redhat.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).