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:
runlevel: N 5
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
Created attachment 768541 [details]
Created attachment 768542 [details]
Created attachment 768543 [details]
Created attachment 768544 [details]
Created attachment 768545 [details]
Created attachment 768546 [details]
Created attachment 768547 [details]
Created attachment 768548 [details]
Created attachment 768549 [details]
Created attachment 768550 [details]
Created attachment 768551 [details]
Not sure if this counts as a resolution but if you add the nightly repository and get the latest version this issue is fixed.
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.
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
Thank you for reporting this bug and we are sorry it could not be fixed.