Opened 14 years ago
Closed 14 years ago
#483 closed defect (fixed)
xapian-core make check fails on Snow Leopard
Reported by: | Tom | Owned by: | Olly Betts |
---|---|---|---|
Priority: | normal | Milestone: | 1.2.1 |
Component: | Test Suite | Version: | 1.2.0 |
Severity: | critical | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Operating System: | Mac OS X |
Description
$ ./configure $ make $ make check ... Running tests with backend "none"... Running test: defaultctor1.../bin/sh: line 1: 33655 Bus error ./runtest ${dir}$tst FAIL: apitest Running test: except1.../bin/sh: line 1: 33677 Bus error ./runtest ${dir}$tst FAIL: internaltest The random seed is 42 Please report the seed when reporting a test failure. Running tests with danish stemmer... Running test: stemrandom.../bin/sh: line 1: 33697 Bus error ./runtest ${dir}$tst FAIL: stemtest Running test: queryparser1.../bin/sh: line 1: 33717 Bus error ./runtest ${dir}$tst FAIL: queryparsertest Running test: termgen1.../bin/sh: line 1: 33737 Bus error ./runtest ${dir}$tst FAIL: termgentest ======================================= 5 of 5 tests failed Please report to http://xapian.org/bugs ======================================= make[4]: *** [check-TESTS] Error 1 make[3]: *** [check-am] Error 2 make[2]: *** [check] Error 2 make[1]: *** [check-recursive] Error 1 make: *** [check] Error 2
OS X 10.6.3 Snow Leopard. 1st generation Intel iMac, 2GHz Core Duo, 2GB RAM.
Change History (6)
comment:2 by , 14 years ago
Summary: | make check fails on Snow Leopard → xapian-core make check fails on Snow Leopard |
---|
comment:3 by , 14 years ago
Wow, that's pretty broken. Can this compiler handle other non-trivial C++ code?
If you run the test under a debugger, can you see where the bus error occurs? Try this:
cd tests ./runtest gdb ./internaltest
And then in gdb:
run bt
comment:4 by , 14 years ago
No problems with building or testing the matchspy branch. Here's the gdb output -
(gdb) bt #0 0x9717c308 in closedir$UNIX2003 () #1 0x0000e0c3 in std::string::_M_data () at /usr/include/c++/4.2.1/bits/basic_string.h:42 #2 0x0000e0c3 in std::string::_M_rep () at /usr/include/c++/4.2.1/bits/basic_string.h:288 #3 0x0000e0c3 in ~basic_string [inlined] () at harness/fdtracker.cc:493 #4 ~basic_string [inlined] () at /usr/include/c++/4.2.1/bits/basic_string.h:493 #5 0x0000e0c3 in FDTracker::~FDTracker (this=0xbffff59c) at harness/fdtracker.cc:44 #6 0x00013ed4 in test_driver::runtest (this=0xbffff724, test=0x263e0) at harness/testsuite.cc:557 #7 0x00014a27 in test_driver::do_run_tests (this=0xbffff724, b={_M_current = 0x0}, e={_M_current = 0x0}) at harness/testsuite.cc:601 #8 0x00014e77 in test_driver::run_tests (this=0xbffff724, b={_M_current = 0x0}, e={_M_current = 0x0}) at harness/testsuite.cc:564 #9 0x00014edf in test_driver::run (tests=0x263e0) at harness/testsuite.cc:775 #10 0x00002662 in main (argc=1, argv=0xbffff808) at internaltest.cc:637
comment:5 by , 14 years ago
Fixed for 1.2.0 by replacing tests/harness/fdtracker.cc with the one from trunk (which has it's own problems on Mac..)
comment:6 by , 14 years ago
Component: | Other → Test Suite |
---|---|
Milestone: | → 1.2.1 |
Resolution: | → fixed |
Status: | new → closed |
OK, so this is already fixed on trunk then.
Note:
See TracTickets
for help on using tickets.