tester: seg fault

After a successful build of revision 127 make reports:-

g++ -c -include calitko -m64 -pipe -g -g -Wall -W -D_REENTRANT  -DQT_XML_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I/usr/lib64/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/QtCore -I/usr/include/QtCore -I/usr/include/QtNetwork -I/usr/include/QtNetwork -I/usr/include/QtGui -I/usr/include/QtGui -I/usr/include/QtXml -I/usr/include/QtXml -I/usr/include -I. -I. -I. -o Utils/moc_Timer.o Utils/moc_Timer.cpp
./tester
.make[2]: *** [calitko] Segmentation fault
I re-ran tester after setting ulimit to generate a core dump of which the top lines are:-

Core was generated by `./tester’.
Program terminated with signal 11, Segmentation fault.
#0  0×0000000000448702 in CppUnit::TestCaller::setUp (this=0×8c7940)
at 3rdParty/cppunit/TestCaller.h:177
177             m_fixture->setUp ();
(gdb) backtrace full
#0  0×0000000000448702 in CppUnit::TestCaller::setUp (this=0×8c7940)
at 3rdParty/cppunit/TestCaller.h:177
No locals.
#1  0×00000000005e4617 in CppUnit::TestCaseMethodFunctor::operator() (this=0×7fff656d5670) at TestCase.cpp:32
No locals.
#2  0×00000000005f2344 in CppUnit::DefaultProtector::protect (this=0×8c79b0, functor=@0×7fff656d5670,
context=@0×7fff656d5670) at DefaultProtector.cpp:15
No locals.
#3  0×00000000005f3239 in CppUnit::ProtectorChain::ProtectFunctor::operator() (this=)
at ProtectorChain.cpp:20
No locals.

Full trace is attached.

Giles

Attached Files:

Would you like to post a relpy?


This post starts a thread.
Follow-ups:
Re: tester: seg fault
Hi Giles, That has happened to be twice I think after merging trees with lots of changes. I simply did make clean all and then it worked. If that does not (more...)