Skip Montanaro wrote: > One of my colleagues with a background in the high performance computing > realm sent me this press release: > > http://www.pathscale.com/ekopath4-open-source-announcement > > I'm not personally familiar with the Pathscale compilers, but thought some > folks here might be and might want to experiment with them. > > Skip
I just rebuilt all my c++ (boost::python) modules using pathscale, and I notice many crash with double-free on exit. According to valgrind, this comes from the pathscale stl: Just a heads-up. ==1927== Invalid free() / delete / delete[] ==1927== at 0x4A0556E: free (vg_replace_malloc.c:366) ==1927== by 0xDA77622: operator delete(void*) (in /home/nbecker/ekopath-4.0.10/lib/4.0.10/x8664/64/libcxxrt.so) ==1927== by 0xD7BB91A: std::allocator<char>::deallocate(char*, unsigned long) (in /home/nbecker/ekopath-4.0.10/lib/4.0.10/x8664/64/libstl.so) ==1927== by 0xD7BB99B: std::string::_C_unlink(char*) (in /home/nbecker/ekopath-4.0.10/lib/4.0.10/x8664/64/libstl.so) ==1927== by 0xD7C4309: std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() (in /home/nbecker/ekopath-4.0.10/lib/4.0.10/x8664/64/libstl.so) ==1927== by 0x3D64438940: __run_exit_handlers (in /lib64/libc-2.14.so) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
