Hi all, I'm seeing the following behaviour with GluCat 0.1.8 on AMD64. ( http://glucat.sf.net ) g++ 3.4.1: OK g++ 4.0.0: using: result: ./configure OK (this uses std::map and -O1) ./configure --with-hash-map: OK (this uses __gnu_cxx::hash_map and -O1) ./configure --enable-debug=no: OK (this uses std::map and -O3) ./configure --with-hash-map --enable-debug=no: compiled program hangs (this uses __gnu_cxx::hash_map and -O3) gdb on the compiled program: bt results in hundreds of stack frames. Looks like the stack has been corrupted. Also it looks like the hang or corruption happens when using iterators with hash_map. I've looked at the test suite and I don't see a test where iterators are used with hash_map. Has anyone ever used g++ 4.0.0 with __gnu_cxx::hash_map and -O3 on AMD64? Do you also have these problems? Is there a bug report for this? I would report a bug except I need a small test case. GluCat is wayyy too big to use as a test case. I'll probably have to use the test suite programs as a basis to cook up a small test case. Or does anyone have a small test case handy? Thanks, Paul Leopardi
