Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 594748 - dev-qt/qt-creator-3.6.1: crashes when opening options
Summary: dev-qt/qt-creator-3.6.1: crashes when opening options
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Davide Pesavento
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-22 08:39 UTC by schmittlauch
Modified: 2016-11-27 15:49 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (file_594748.txt,6.66 KB, text/plain)
2016-09-22 08:39 UTC, schmittlauch
Details
gdb output (file_594748.txt,510 bytes, text/plain)
2016-09-22 08:42 UTC, schmittlauch
Details
backtrace of qt-creator after crashing (qtcreator.log,6.10 KB, text/plain)
2016-09-25 12:41 UTC, schmittlauch
Details
User patch to correct segfault (qt-creator-3.6.1-variablechooser.patch,551 bytes, patch)
2016-11-22 05:21 UTC, Herb Miller Jr.
Details | Diff
Updated patch also prevent remaining segfaults (qt-creator-3.6.1-variablechooser.patch,1.00 KB, patch)
2016-11-27 15:49 UTC, Herb Miller Jr.
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description schmittlauch 2016-09-22 08:39:18 UTC
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
Comment 1 schmittlauch 2016-09-22 08:42:15 UTC
Created attachment 447300 [details]
gdb output
Comment 2 Davide Pesavento gentoo-dev 2016-09-22 17:44:03 UTC
(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
Comment 3 schmittlauch 2016-09-25 12:40:37 UTC
Sorry about that, here's a better backtrace, I hope this is helpful.
Comment 4 schmittlauch 2016-09-25 12:41:24 UTC
Created attachment 447844 [details]
backtrace of qt-creator after crashing
Comment 5 Anton 2016-11-17 15:41:21 UTC
I have this segfault with exactly same stack trace when trying to open existing project
Comment 6 Herb Miller Jr. 2016-11-22 05:21:46 UTC
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?
Comment 7 Davide Pesavento gentoo-dev 2016-11-22 10:28:41 UTC
(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!
Comment 8 Herb Miller Jr. 2016-11-24 00:15:02 UTC
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?
Comment 9 Davide Pesavento gentoo-dev 2016-11-24 01:06:18 UTC
(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.
Comment 10 stqn 2016-11-27 13:26:04 UTC
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?
Comment 11 Herb Miller Jr. 2016-11-27 15:49:16 UTC
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.