From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
Cole Robinson <crobinso@redhat.com>
Subject: Re: hw-display-qxl.so: undefined symbol: qemu_qxl_io_log_semaphore
Date: Thu, 20 Aug 2020 09:46:32 +0100 [thread overview]
Message-ID: <20200820084632.GB109518@redhat.com> (raw)
In-Reply-To: <20200820082943.fryka3gsjmw2muc5@sirius.home.kraxel.org>
On Thu, Aug 20, 2020 at 10:29:43AM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > If systemtap won't change, then to fix this, for any foo.c
> > that will be in a module, we need a separate 'foo.trace'
> > file that generates a .o that is directly linked to the
> > foo.so, not the qemu-system-x86_64 binary.
>
> I think that is the plan anyway.
It looks like we have no choice. The systemtap maintainers don't want to
change to make the semaphore symbols in the binary visible to modules.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2020-08-20 8:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 21:10 hw-display-qxl.so: undefined symbol: qemu_qxl_io_log_semaphore Cole Robinson
2020-07-29 12:50 ` Stefan Hajnoczi
2020-08-12 15:46 ` Cole Robinson
2020-08-17 5:39 ` Gerd Hoffmann
2020-08-17 18:06 ` Cole Robinson
2020-08-18 7:22 ` Gerd Hoffmann
2020-08-18 12:15 ` Daniel P. Berrangé
2020-08-18 12:33 ` Daniel P. Berrangé
2020-08-20 8:29 ` Gerd Hoffmann
2020-08-20 8:46 ` Daniel P. Berrangé [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=20200820084632.GB109518@redhat.com \
--to=berrange@redhat.com \
--cc=crobinso@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).