From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Akihiko Odaki" <akihiko.odaki@gmail.com>,
"Marc-André Lureau" <marcandre.lureau@gmail.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Thomas Huth" <thuth@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>
Subject: Re: tests/qtest: Is vnc-display-test supposed to work on Darwin?
Date: Thu, 19 Jan 2023 14:14:35 +0000 [thread overview]
Message-ID: <Y8lQS9/UrF+sZN0M@redhat.com> (raw)
In-Reply-To: <Y8kw6X6keB5l53nl@redhat.com>
On Thu, Jan 19, 2023 at 12:00:41PM +0000, Daniel P. Berrangé wrote:
> On Thu, Jan 19, 2023 at 12:49:48PM +0100, Philippe Mathieu-Daudé wrote:
> > So to detect makecontext() I have to add
> > --extra-cflags=-mmacosx-version-min=10.5 but then linking fails with
> > multiple "$LIBNAME was built for newer macOS version (13.0) than being
> > linked (11.0)".
>
> Yes, ucontext has been deprecated forever on macOS, but in practice it
> has still been functional if you define _XOPEN_SOURCE, which is what
> gtk-vnc has done traditionally.
>
> I presume this is on the aarch64 macOS though, and so all bets are off
> wrt ucontext backend unless someone knows it works correctly with the
> m1 port. I fear that's not the case though, given the wierd error
> scenario we're hitting in gtk-vnc.
Yep, I've confirmed there's something broken with gtk-vnc. When we
call 'getcontext' is corrupts memory in gtk-vnc structs. This makes
me believe that the defined 'struct ucontext_t' is too small for use
with 'getcontext' on macOS aarch64 platforms.
With 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 :|
next prev parent reply other threads:[~2023-01-19 14:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 9:49 tests/qtest: Is vnc-display-test supposed to work on Darwin? Philippe Mathieu-Daudé
2022-12-05 7:51 ` Marc-André Lureau
2023-01-19 11:01 ` Philippe Mathieu-Daudé
2023-01-19 11:16 ` Daniel P. Berrangé
2023-01-19 11:21 ` Philippe Mathieu-Daudé
2023-01-19 11:33 ` Daniel P. Berrangé
2023-01-19 11:49 ` Philippe Mathieu-Daudé
2023-01-19 12:00 ` Daniel P. Berrangé
2023-01-19 14:14 ` Daniel P. Berrangé [this message]
2023-01-19 11:29 ` Philippe Mathieu-Daudé
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=Y8lQS9/UrF+sZN0M@redhat.com \
--to=berrange@redhat.com \
--cc=akihiko.odaki@gmail.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.