Re: Trying to use gdb on OS X
- Posted by jaygade Jun 10, 2013
- 3142 views
Continuing on.
Test results summary: FAIL: t_callc.e FAIL: t_filesys.e FAIL: t_io.e FAIL: t_locale.e FAIL: t_net_http.e FAIL: t_socket.e Files (run: 147) (failed: 6) (96% success)
First eutest failure is for t_callc.e
interpreting t_callc.e: CMD 'eui -d UNITTEST -batch t_callc.e ' failed: can open lib818.dll, expected: TRUE but got: FALSE /Users/jason/Dropbox/src/openeuphoria/stable/osx/include/std/unittest.e:454 in procedure assert() can open lib818.dll ... called from /Users/jason/Dropbox/src/openeuphoria/stable/osx/tests/t_callc.e:148 --> See ex.err failed: unittesting crashed, expected: TRUE but got: FALSE 13 tests run, 11 passed, 2 failed, 85% success FAILURE: t_callc.e EUPHORIA error with status 256 Test results summary: FAIL: t_callc.e Files (run: 1) (failed: 1) (0% success)
Looking through the history, this was a 4.1 thing? There is no lib818.dll or lib818.c included with the 4.0 branch.
t_filesys.e fails. It looks like it has something to do with wildcard expansion.
interpreting t_filesys.e: CMD '/Users/jason/bin/eui -d UNITTEST -batch t_filesys.e ' failed: dir() #5, expected: "anything but '-1'" but got: -1 137 tests run, 136 passed, 1 failed, 99% success FAILURE: t_filesys.e program died with status 256
t_io.e fails. It looks like seek doesn't work on OS X like it does on other BSDs.
interpreting t_io.e: CMD '/Users/jason/bin/eui -d UNITTEST -batch t_io.e ' failed: Seek STDIN, expected: 1 but got: 0 failed: Seek STDOUT, expected: 1 but got: 0 failed: Seek STDERR, expected: 1 but got: 0 71 tests run, 68 passed, 3 failed, 96% success FAILURE: t_io.e program died with status 256
More to come. Time to quit for tonight.