From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15461] QtVirtualKeyboard segfaults
Date: Tue, 21 Mar 2023 13:42:51 +0000 [thread overview]
Message-ID: <bug-15461-163-mmCyzi0BVI@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15461-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15461
--- Comment #2 from Alexis Lothoré <alexis.lothore@bootlin.com> ---
Hi. I indeed encounter the same kind of issue in a Qt Quick project on Armv7
target
* with Buildroot 2023.02 and Bootlin Toolchain 2022.08, Qt project crashes deep
in qqmlcrashpropertycache.h (in an inlined function)
* trying to build without optimizations (to allow debugging), the application
does not crash anymore
* switching back to Bootlin toolchain 2021.11, the application works, even with
optimizations enabled
* I tried to switch to buildroot internal toolchain BUT with components
versions (gcc, glibc, binutils, kernel headers) from bootlin toolchain 2022.08
=> it still crashes, so it is probably not the Bootlin build of the toolchain
which is the culprit
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-03-21 13:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 2:43 [Buildroot] [Bug 15461] New: QtVirtualKeyboard segfaults bugzilla
2023-03-21 13:23 ` [Buildroot] [Bug 15461] " bugzilla
2023-03-21 13:42 ` bugzilla [this message]
2023-03-22 0:53 ` bugzilla
2023-03-22 2:08 ` bugzilla
2023-03-22 13:51 ` bugzilla
2023-03-22 16:36 ` bugzilla
2023-06-21 13:08 ` bugzilla
2023-06-21 14:46 ` bugzilla
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=bug-15461-163-mmCyzi0BVI@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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 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.