Hide Forgot
Version-Release number of selected component: codeblocks-16.01-1.fc24 Additional info: reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: codeblocks crash_function: wxStringBase::operator= executable: /usr/bin/codeblocks global_pid: 20519 kernel: 4.8.4-200.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 wxStringBase::operator= at src/common/string.cpp:779 #1 wxString::operator= at /usr/include/wx-2.8/wx/string.h:659 #2 CCManager::OnShowCallTip at ccmanager.cpp:919 #3 Manager::ProcessEvent at manager.cpp:263 #4 CCManager::OnDeferredCallTipShow at ccmanager.cpp:1060 #5 wxEvtHandler::ProcessEventIfMatches at src/common/event.cpp:1239 #6 wxEvtHandler::SearchDynamicEventTable at src/common/event.cpp:1421 #7 wxEvtHandler::ProcessEvent at src/common/event.cpp:1297 #8 wxEvtHandler::ProcessPendingEvents at src/common/event.cpp:1196 #9 wxAppConsole::ProcessPendingEvents at src/common/appbase.cpp:294
Created attachment 1216744 [details] File: backtrace
Created attachment 1216745 [details] File: cgroup
Created attachment 1216746 [details] File: core_backtrace
Created attachment 1216747 [details] File: dso_list
Created attachment 1216748 [details] File: environ
Created attachment 1216749 [details] File: exploitable
Created attachment 1216750 [details] File: limits
Created attachment 1216751 [details] File: maps
Created attachment 1216752 [details] File: mountinfo
Created attachment 1216753 [details] File: namespaces
Created attachment 1216754 [details] File: open_fds
Created attachment 1216755 [details] File: proc_pid_status
Created attachment 1216756 [details] File: var_log_messages
It looks like you hit a longs standing, hard to reproduce upstream bug: http://forums.codeblocks.org/index.php/topic,20489.0.html . Unfortunately, I'm not familiar with this part of C::B. Do you have a project you can share (even via private mail), to reproduce this issue ? Or other steps to reproduce it ?
(In reply to Jens Lody from comment #14) > It looks like you hit a longs standing, hard to reproduce upstream bug: > http://forums.codeblocks.org/index.php/topic,20489.0.html . > > Unfortunately, I'm not familiar with this part of C::B. > > Do you have a project you can share (even via private mail), to reproduce > this issue ? > Or other steps to reproduce it ? I'm sorry, I didn't manage to reproduce it in any way. Please close this bug report, if there is nothing to be done.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.