Bug 981080

Summary: [abrt] codeblocks-10.05-10.fc18: path_split: Process /usr/bin/codeblocks was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Dylan1473
Component: codeblocksAssignee: Dan Horák <dan>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: dan, i
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:bf9606a769d4357771fc57deedeaad9181d875b2
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 22:03:41 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: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
File: xsession_errors none

Description Dylan1473 2013-07-04 00:53:28 UTC 
Description of problem:
This problem occurred when I was trying to compile a C++ project. The project was very basic, just filling a vector with three strings and printing them using an auto for loop to test that it was working with the c++11 standard. It occurred twice in a row. Projects compile fine with c++11 in eclipse-cdt and presumably with just gcc by itself as well.

Version-Release number of selected component:
codeblocks-10.05-10.fc18

Additional info:
reporter:       libreport-2.1.5
backtrace_rating: 4
cmdline:        /usr/bin/codeblocks
crash_function: path_split
executable:     /usr/bin/codeblocks
kernel:         3.7.9-205.fc18.x86_64
runlevel:       N 5
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 path_split at pathsplit.c:82
 #1 depsTimeStamp at depslib.c:142
 #2 DirectCommands::IsObjectOutdated at directcommands.cpp:872
 #3 DirectCommands::GetTargetCompileCommands at directcommands.cpp:431
 #4 DirectCommands::GetCompileCommands at directcommands.cpp:383
 #5 CompilerGCC::BuildStateManagement at compilergcc.cpp:2408
 #6 CompilerGCC::DoRunQueue at compilergcc.cpp:1164
 #7 CompilerGCC::DoBuild at compilergcc.cpp:2729
 #8 CompilerGCC::Build at compilergcc.cpp:2740
 #9 CompilerGCC::OnCompile at compilergcc.cpp:3024
Comment 1 Dylan1473 2013-07-04 00:53:36 UTC 
Created attachment 768541 [details]
File: backtrace
Comment 2 Dylan1473 2013-07-04 00:53:39 UTC 
Created attachment 768542 [details]
File: cgroup
Comment 3 Dylan1473 2013-07-04 00:53:42 UTC 
Created attachment 768543 [details]
File: core_backtrace
Comment 4 Dylan1473 2013-07-04 00:53:46 UTC 
Created attachment 768544 [details]
File: dso_list
Comment 5 Dylan1473 2013-07-04 00:53:53 UTC 
Created attachment 768545 [details]
File: environ
Comment 6 Dylan1473 2013-07-04 00:53:56 UTC 
Created attachment 768546 [details]
File: limits
Comment 7 Dylan1473 2013-07-04 00:53:59 UTC 
Created attachment 768547 [details]
File: maps
Comment 8 Dylan1473 2013-07-04 00:54:02 UTC 
Created attachment 768548 [details]
File: open_fds
Comment 9 Dylan1473 2013-07-04 00:54:05 UTC 
Created attachment 768549 [details]
File: proc_pid_status
Comment 10 Dylan1473 2013-07-04 00:54:08 UTC 
Created attachment 768550 [details]
File: var_log_messages
Comment 11 Dylan1473 2013-07-04 00:54:11 UTC 
Created attachment 768551 [details]
File: xsession_errors
Comment 12 Dylan1473 2013-07-04 01:10:03 UTC 
Not sure if this counts as a resolution but if you add the nightly repository and get the latest version this issue is fixed.
Comment 13 Fedora End Of Life 2013-12-21 14:14:18 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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.
Comment 14 Fedora End Of Life 2014-02-05 22:03:41 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.