Created attachment 447298 [details] emerge --info dev-qt/qt-creator-3.6.1 crashes when opening the settings. How to reproduce: 1. Run qtcreator 2. Open the settings page via 'Tools' -> 'Options' 3. See qtcreator crash with a segfault
Created attachment 447300 [details] gdb output
(In reply to t.schmittlauch+gentoo from comment #1) > Created attachment 447300 [details] > gdb output This is completely useless. Please see this page to obtain a meaningful backtrace: https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces
Sorry about that, here's a better backtrace, I hope this is helpful.
Created attachment 447844 [details] backtrace of qt-creator after crashing
I have this segfault with exactly same stack trace when trying to open existing project
Created attachment 454008 [details, diff] User patch to correct segfault In version 4.1.0 they added a guard in variablechooser.cpp that seems to prevent this. Can we backport it to 3.6.1? After rebuilding with the attached patch I'm able to open Tools -> Options without a segfault, but Build & Run and Debugger options still segfault. Should this be tackled in this bug or a new one created for those?
(In reply to Herb Miller Jr. from comment #6) > Created attachment 454008 [details, diff] [details, diff] > User patch to correct segfault > > In version 4.1.0 they added a guard in variablechooser.cpp that seems to > prevent this. Can we backport it to 3.6.1? > We could, but it wouldn't make much sense since we wouldn't stabilize the revbumped version. I suggest you simply use 4.1.0, we will try to stabilize it ASAP. > After rebuilding with the attached patch I'm able to open Tools -> Options > without a segfault, but Build & Run and Debugger options still segfault. > Should this be tackled in this bug or a new one created for those? It's better to report a bug upstream since it seems a real upstream bug. Mention the patch above or the commit that introduced the guard, maybe a similar one will also fix the second crash. Thanks!
Upstream bug already exists: https://bugreports.qt.io/browse/QTCREATORBUG-15966 Not sure if I'm reading this right. Are they saying it was already fixed in 3.6.1, or the fix was targeted for 4.1.0, meaning it will never be applied to 3.6.1? If the former, why/how is the ebuild still pulling down the broken version?
(In reply to Herb Miller Jr. from comment #8) > Upstream bug already exists: > https://bugreports.qt.io/browse/QTCREATORBUG-15966 > > Not sure if I'm reading this right. Are they saying it was already fixed in > 3.6.1, or the fix was targeted for 4.1.0, meaning it will never be applied > to 3.6.1? > > If the former, why/how is the ebuild still pulling down the broken version? Upstream bug mentions commit fb137ade7d93955a930ca9ba21f55dfd6b599f08, which is contained in v4.0.0-rc1 and later. So no, 3.6.1 does NOT have the fix. As I suggested earlier, please upgrade to a newer (~arch) version.
When looking for bugs affecting Qt Creator this one doesn’t appear because it has been marked "resolved" (I guess). So I spent hours searching how to stop Qt Creator from crashing and building new versions of Qt and Qt Creator. Maybe it shouldn’t be closed as long as this is still a problem with current stable Qt Creator and Qt packages?
Created attachment 454526 [details, diff] Updated patch also prevent remaining segfaults Including an updated patch that corrects the remaining segfaults in case other users discover this bug and would like to add as user patch instead of upgrading.