________________________________________ From: [email protected] [[email protected]] On Behalf Of Lazy Burd [[email protected]]
On Wed, Apr 28, 2010 at 1:05 AM, Daniel <[email protected]> wrote: > (Sorry for my english) > Hi, I was making a build and return an error : > > [TEST]:SipOutputProcessorTest::testProcess6xxResponses > [TEST]:SipOutputProcessorTest::testPriorityOrdering > [TEST]:SipPresenceEventTest::testGetPresencePackage > [TEST]:SipPresenceEventTest::testPresencePackageParser > [TEST]:SipProxyMessageTest::testNoRouteLocal > [TEST]:SipProxyMessageTest::testOneRouteLocal > /bin/sh: line 5: 2604 Segmentation fault ${dir}$tst More than an error, a juicy segfault! In the test directory is an executable you can run thru gdb or ddd and will direct you to the bad line. Are you familiar w/gdb or ddd? if not you may need some additional help here. _______________________________________________ Specifically, look for .../sipXtackLib/src/test/.libs/lt-testsuite. Run that using your favorite debugger. When it segfaults, get the backtrace of the failing thread. Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
