Bug 1033929

Summary: [abrt] qt-creator-2.8.1-1.fc19: QWidget::setParent(QWidget*): Process /usr/bin/qtcreator was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: backdoor03
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: backdoor03, itamar, jreznik, ltinkl, manisandro, rdieter
Target Milestone: ---Flags: manisandro: needinfo? (backdoor03)
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/1c8062f56af8df3429dcd0cf55856ab99375aa1e
Whiteboard: abrt_hash:e5ee0c8a153d0874df5c7da23bc429d5723e268c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-30 20:50:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
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 backdoor03 2013-11-24 13:09:42 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: QWidget::setParent(QWidget*)
executable:     /usr/bin/qtcreator
kernel:         3.11.9-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 QWidget::setParent(QWidget*) at /lib64/libQtGui.so.4
 #1 Analyzer::Internal::AnalyzerMode::~AnalyzerMode() at /usr/lib64/qtcreator/plugins/QtProject/libAnalyzerBase.so
 #2 ExtensionSystem::IPlugin::~IPlugin() at /usr/bin/../lib64/qtcreator/libExtensionSystem.so.1
 #3 Analyzer::Internal::AnalyzerPlugin::~AnalyzerPlugin() at /usr/lib64/qtcreator/plugins/QtProject/libAnalyzerBase.so
 #4 ExtensionSystem::Internal::PluginSpecPrivate::kill() at /usr/bin/../lib64/qtcreator/libExtensionSystem.so.1
 #5 ExtensionSystem::Internal::PluginManagerPrivate::loadPlugin(ExtensionSystem::PluginSpec*, ExtensionSystem::PluginSpec::State) at /usr/bin/../lib64/qtcreator/libExtensionSystem.so.1
 #6 ExtensionSystem::Internal::PluginManagerPrivate::deleteAll() at /usr/bin/../lib64/qtcreator/libExtensionSystem.so.1
 #7 ExtensionSystem::Internal::PluginManagerPrivate::shutdown() at /usr/bin/../lib64/qtcreator/libExtensionSystem.so.1
 #8 QMetaObject::activate at kernel/qobject.cpp:3547
 #9 QCoreApplication::aboutToQuit at .moc/release-shared/moc_qcoreapplication.cpp:144
Comment 1 backdoor03 2013-11-24 13:09:51 UTC 
Created attachment 828286 [details]
File: backtrace
Comment 2 backdoor03 2013-11-24 13:09:55 UTC 
Created attachment 828287 [details]
File: cgroup
Comment 3 backdoor03 2013-11-24 13:09:59 UTC 
Created attachment 828288 [details]
File: core_backtrace
Comment 4 backdoor03 2013-11-24 13:10:03 UTC 
Created attachment 828289 [details]
File: dso_list
Comment 5 backdoor03 2013-11-24 13:10:07 UTC 
Created attachment 828290 [details]
File: environ
Comment 6 backdoor03 2013-11-24 13:10:11 UTC 
Created attachment 828291 [details]
File: exploitable
Comment 7 backdoor03 2013-11-24 13:10:15 UTC 
Created attachment 828292 [details]
File: limits
Comment 8 backdoor03 2013-11-24 13:10:19 UTC 
Created attachment 828293 [details]
File: maps
Comment 9 backdoor03 2013-11-24 13:10:23 UTC 
Created attachment 828294 [details]
File: open_fds
Comment 10 backdoor03 2013-11-24 13:10:27 UTC 
Created attachment 828295 [details]
File: proc_pid_status
Comment 11 backdoor03 2013-11-24 13:10:32 UTC 
Created attachment 828296 [details]
File: var_log_messages
Comment 12 Sandro Mani 2013-11-24 15:15:38 UTC 
Unfortunately the backtrace is incomplete due to missing debug symbols. Did you generate the backtrace locally or use the retrace server? Is the bug reproducible? If so, could you provide steps to reproduce it? Otherwise I fear that there is not enough information to work on.
Comment 13 Sandro Mani 2013-11-30 20:50:26 UTC 
Closing due to unresponsive reporter and insufficient data. Please reopen if more information can be provided.