From: Daniel R. <da...@ru...> - 2007-11-28 11:23:26
|
Fletcher, John P wrote: > Dear All > > I have not run any tests. What I do see is that metakit has moved on in version, I think to 2.4.9.7 while E4Graph which uses it has not. It may be useful to note which version of metakit is being used in the different tests. Some Linux distributions e.g. fedora6 actually have an option to install metakit and metakit-devel, but not in that case the python or tcl interfaces. > > Best wishes > > John > True but that would not explain why I am experiencing problems on 1 setup and not the other, both are running metakit-2.4.0.3_4 Heres an update on the gdb output, i built the test libs with ggdb3: #7 0x28101c42 in e4_StorageImpl::NotReferenced () from /usr/ports/devel/e4graph/work/e4graph-1.0a11/all/../builds/i386-portbld-freebsd7.0/libs/libe4graph.so #8 0x280ee837 in e4_RefCount::~e4_RefCount () from /usr/ports/devel/e4graph/work/e4graph-1.0a11/all/../builds/i386-portbld-freebsd7.0/libs/libe4graph.so #9 0x0805aafe in test_storage5 () at e4graph.h:716 #10 0x0805c996 in test_storage () at ./../src/teststorage.cpp:1494 #11 0x0804ca19 in main (ac=Cannot access memory at address 0x5 And in a second attempt, added some more output; looks like it segfaults at step 6... test storage5 passed step 1 test storage5 passed step 2.a test storage5 passed step 3 test storage5 passed step 3.a test storage5 passed step 4 test storage5 passed step 5 > Jeff Rose wrote: > >> Hello out there, >> Anyone still here? I thought I'd try to knock the dust of the >> mailing list here. Are people still using e4Graph? I'm getting a >> segfault when running the unit tests on a fresh build in Ubuntu Gutsy, >> and the python bindings don't build because of a syntax error. Is this >> library just getting old and unloved? >> >> > Hey Jeff, First off, I love it. Now, about the unit tests, which I've > never actually ran until tonight. > > For FreeBSD 6.3-PRERELEASE with gcc 3.4.6 > > I get this output when running the tests: > Running e4_DString tests: ..... > Running e4_Refcount tests: .... > Running e4_Storage tests: ..................... > Running e4_Node tests: ........................................... > Running e4_Vertex tests: ............... > Running e4_StorageVisitor tests: .. > Running e4_NodeVisitor tests: ....... > Running e4_VertexVisitor tests: ............................ > Running callback tests: ...... > Running detach tests: ........ > > Which I believe means everything passed. > > However on 7.0-BETA3 FreeBSD 7.0-BETA3 with > gcc version 4.2.1 20070719 AND > gcc version 4.2.3 20071024 I get: > > Running e4_DString tests: ..... > Running e4_Refcount tests: .... > Running e4_Storage tests: ...pure virtual method called > terminate called without an active exception > Abort trap: 6 (core dumped) > > And some gdb: > #0 0x282ef0d7 in kill () from /lib/libc.so.7 > #1 0x282ef036 in raise () from /lib/libc.so.7 > #2 0x282edc4a in abort () from /lib/libc.so.7 > #3 0x28175b80 in __gnu_cxx::__verbose_terminate_handler () from > /usr/lib/libstdc++.so.6 > #4 0x2817a02a in std::set_unexpected () from /usr/lib/libstdc++.so.6 > #5 0x2817a072 in std::terminate () from /usr/lib/libstdc++.so.6 > #6 0x281c3b55 in __cxa_pure_virtual () from /usr/lib/libstdc++.so.6 > #7 0x28101c42 in e4_StorageImpl::NotReferenced () from > /usr/local/lib/libe4graph.so > #8 0x280ee837 in e4_RefCount::~e4_RefCount () from > /usr/local/lib/libe4graph.so > #9 0x08070b2e in test_storage5 () > #10 0x080729c6 in test_storage () > #11 0x0804ca19 in main () > > If someone can do something with the output I'll rebuild with debugging > symbols. > > Is this the same spot your unit test fail in Linux? > > Cheers, > Daniel Rucci > > |