[CMake] Cvs version 'Segmentation Fault'

[Bill Hoffman]

Baptiste Derongs wrote:
>> Would it be possible for you to run ctest in gdb or some debugger and
>> send a call stack of the crash?
> 
> Here is the stack juste after Ctest crashed
> 
> (gdb) bt
> #0  0x00d5175d in std::string::append () from /usr/lib/libstdc++.so.6
> #1  0x00d51972 in std::string::operator+= () from /usr/lib/libstdc++.so.6
> #2  0x081c5b01 in cmCTestTestHandler::ProcessOneTest ()
> #3  0x081c768e in cmCTestTestHandler::ProcessDirectory ()
> #4  0x081c34fa in cmCTestTestHandler::ProcessHandler ()
> #5  0x081e3fe4 in cmCTestHandlerCommand::InitialPass ()
> #6  0x081b3707 in cmCommand::InvokeInitialPass ()
> #7  0x0822f1f3 in cmMakefile::ExecuteCommand ()
> #8  0x0822ffc3 in cmMakefile::ReadListFile ()
> #9  0x081aefe8 in cmCTestScriptHandler::ReadInScript ()
> #10 0x081afbf9 in cmCTestScriptHandler::RunConfigurationScript ()
> #11 0x081adc3d in cmCTestScriptHandler::ProcessHandler ()
> #12 0x08171fda in cmCTest::Run ()
> #13 0x081620cb in main ()
> 
> Uncannily in gdb the crash appends earlier, not only near the 99th
> one. This time it was just after the 25th test.
> 
> If this stack result is not enough I can send you more (if you tell me what....)
> 

If you could build cmake with Debug (-g) it would be more helpful... 
Also, if you add -VV to ctest what are the last 100 lines of output?


-Bill