From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15461] QtVirtualKeyboard segfaults
Date: Wed, 22 Mar 2023 13:51:09 +0000 [thread overview]
Message-ID: <bug-15461-163-pHsqtx6a95@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 #5 from Alexis Lothoré <alexis.lothore@bootlin.com> ---
> Thank you for good comments. I've been trying to play with optimization level, any comments how and what you do on optimization in details would be appreciated.
If you are still interested in this option, I simply added the following to
package/qt5/qt5declarative/qt5declarative.mk:
QT5DECLARATIVE_CONF_OPTS += QMAKE_CXXFLAGS=-O0
I also tried with GCC12, with which the crash is still occuring, so the issue
is still in GCC12. I guess next step will be to try to isolate a qt quick
sample able to reproduce the issue to track the exact issue and/or share it
with GNU people
--
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-22 13:51 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
2023-03-22 0:53 ` bugzilla
2023-03-22 2:08 ` bugzilla
2023-03-22 13:51 ` bugzilla [this message]
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-pHsqtx6a95@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox