Bug 1031272

Summary: [abrt] qt-creator-2.8.1-1.fc19: KFileDialog::KFileDialog(KUrl const&, QString const&, QWidget*, QWidget*): Process /usr/bin/qtcreator was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: redhat
Component: qt-creatorAssignee: Itamar Reis Peixoto <itamar>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: itamar, jreznik, ltinkl, manisandro, rdieter, redhat
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/d0141e286af59f9bae225040e723b6337caa1bd6
Whiteboard: abrt_hash:53da6ce0d9de86d8fff5b7696033c4af3618dde2
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-17 22:33:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description redhat 2013-11-16 10:09:36 UTC 
Version-Release number of selected component:
qt-creator-2.8.1-1.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/bin/qtcreator
crash_function: KFileDialog::KFileDialog(KUrl const&, QString const&, QWidget*, QWidget*)
executable:     /usr/bin/qtcreator
kernel:         3.11.7-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1001

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 KFileDialog::KFileDialog(KUrl const&, QString const&, QWidget*, QWidget*) at /lib64/libkio.so.5
 #1 KFileDialogQtOverride::getOpenFileNames(QWidget*, QString const&, QString const&, QString const&, QString*, QFlags<QFileDialog::Option>) at /lib64/libkio.so.5
 #2 QFileDialog::getOpenFileNames at dialogs/qfiledialog.cpp:1871
 #3 Core::DocumentManager::getOpenFileNames at documentmanager.cpp:797
 #4 Core::EditorManager::getOpenFileNames at editormanager/editormanager.cpp:1685
 #5 Core::Internal::MainWindow::openFile at mainwindow.cpp:802
 #6 Core::Internal::MainWindow::qt_static_metacall at .moc/release-shared/moc_mainwindow.cpp:130
 #7 QMetaObject::activate at kernel/qobject.cpp:3547
 #8 QAction::triggered at .moc/release-shared/moc_qaction.cpp:276
 #9 QMetaObject::activate at kernel/qobject.cpp:3547
Comment 1 redhat 2013-11-16 10:09:46 UTC 
Created attachment 824857 [details]
File: backtrace
Comment 2 redhat 2013-11-16 10:09:49 UTC 
Created attachment 824858 [details]
File: cgroup
Comment 3 redhat 2013-11-16 10:09:53 UTC 
Created attachment 824859 [details]
File: core_backtrace
Comment 4 redhat 2013-11-16 10:09:57 UTC 
Created attachment 824860 [details]
File: dso_list
Comment 5 redhat 2013-11-16 10:10:01 UTC 
Created attachment 824861 [details]
File: environ
Comment 6 redhat 2013-11-16 10:10:04 UTC 
Created attachment 824862 [details]
File: exploitable
Comment 7 redhat 2013-11-16 10:10:08 UTC 
Created attachment 824863 [details]
File: limits
Comment 8 redhat 2013-11-16 10:10:14 UTC 
Created attachment 824864 [details]
File: maps
Comment 9 redhat 2013-11-16 10:10:18 UTC 
Created attachment 824865 [details]
File: open_fds
Comment 10 redhat 2013-11-16 10:10:21 UTC 
Created attachment 824866 [details]
File: proc_pid_status
Comment 11 redhat 2013-11-16 10:10:25 UTC 
Created attachment 824867 [details]
File: var_log_messages
Comment 12 Sandro Mani 2013-11-16 10:26:48 UTC 
Is this reproducible? Do you remember what you were doing before the crash occurred?
Comment 13 redhat 2013-11-17 11:20:40 UTC 
(In reply to Sandro Mani from comment #12)
> Is this reproducible? Do you remember what you were doing before the crash
> occurred?

Unfortunately this crash happened kind of out of the blue. I was trying to open a project. Therefore I opened the "File" menu and was about to hit the "Project open" entry (or maybe clicked it already).

After starting Qtcreator again the crash did not occur anymore.
Comment 14 Sandro Mani 2013-11-17 12:54:52 UTC 
Unfortunately the backtrace is not complete, since the debug symbols are out-of-date. Did you generate the backtrace locally or did you have the rectrace server generate it for you?
Comment 15 redhat 2013-11-17 13:00:55 UTC 
(In reply to Sandro Mani from comment #14)
> Unfortunately the backtrace is not complete, since the debug symbols are
> out-of-date. Did you generate the backtrace locally or did you have the
> rectrace server generate it for you?

The backtrace was generated locally as the retrace server rejected to do it, because of the size. ABRT downloaded a lot of stuff for doing this. Could it be a problem that the debug symbols weren't installed when the crash occured?
Comment 16 Sandro Mani 2013-11-17 13:39:07 UTC 
It seems more like you updated some packages but the corresponding debuginfo package were not updated (notice all the "warning: the debug information found in *** does not match *** (CRC mismatch)." warnings in the backtrace).

Anyhow, perhaps there is still enough info to work out what was happening, I'll have a look.
Comment 17 Sandro Mani 2013-11-17 22:33:13 UTC 
Unfortunately there is is not enough to figure out what is going on (in particular, the kdelibs debuginfo package was not installed, so there is no info about the actual exact place where the crash occured). I'll close this as "insufficient data", please feel free to reopen if you hit this again and can provide a more complete backtrace. Thanks!