https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118748
Sam James <sjames at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |14.3
See Also| |https://bugreports.qt.io/br
| |owse/QTBUG-132447
Keywords| |wrong-code
Summary|Segmentation fault in qt |[14/15 regression]
|apps in aarch64 |Segmentation fault in qt
| |apps in aarch64
--- Comment #1 from Sam James <sjames at gcc dot gnu.org> ---
I'm not sure there's much we can do here with this as-is. I don't understand
how Kvantum could cause that (does it install some plugin?) and it's not clear
to me how to even reproduce even if I could spend that amount of time on it.
Thiago would be best-placed to say who is most likely to blame, and he wasn't
able to deduce it in the Qt bug AFAICT. His comment there makes it sound like
some corrupt config file or plugin gets installed/created by Kvantum and that
breaks everything else.
Manually building Kvantum with GCC 13 and then 14 and confirming it works with
13 and fails with 14 would be a start.
