-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segfault in libQt5Gui.so.5 when qview is compiled with -stdlib=libc++ #395
Comments
Are you using wayland? |
No, X11 (i3) |
Same result when compiling Qt with GCC 10.2.0. Are you able to verify that compiling qview with Clang results in a segfault? |
Just tried with clang and there was no segfault. Maybe it's because of -O3? I am seeing in your backtrace: libQt5Gui.so.5 was compiled with optimization - stepping may behave oddly; variables may not be available. |
That message is present at all |
I am on arch linux with clang 11.0.1--maybe it's clang 12? |
Oh, I see you already mentioned that. Nevermind. |
@telans This happens also with |
Yes. No change after multiple |
@novomesk I've narrowed this down to the flags |
@telans So far I was unable to reproduce problem. I tried I have |
@jurplel I filed a bug with Qt and someone there responded with something that may be a fix: https://bugreports.qt.io/browse/QTBUG-91510 I'm not sure why you can't reproduce it novomesk, maybe because I use -stdlib=libc++ too? Update: In fact it seems to be only libc++ causing it, sorry for the confusion |
I just got schooled, I suppose |
UPDATE: Fixed by using
-stdlib=libstdc++
instead of-stdlib=libc++
Environment:
clang -v
:Information:
When qview is compiled with Clang the program fails to start with a segfault. Below is a backtrace of the segfault, not sure how useful it is. To me it looks like this might be a Qt issue though I haven't seen this issue in any other Qt programs.
The rest of Qt is also compiled with Clang. I will test and update whether or not building qtcore etc with GCC fixes the issue.
Using a different Clang version (i.e 11) has no effect.
Backtrace:
The text was updated successfully, but these errors were encountered: