Beman, thanks for the reply.

Boost.Filesystem doesn't directly do any multi-threading, but it does use shared_ptr. Are the shared_ptr tests working for you? If not, you need to resolve those problems before trying Boost.Filesystem.

I ran the tests in libs/smart_ptr/test, including the longer test of "shared_ptr_alloc_test", and they passed with flying colors (except the two intentional compile failures; those threw me for a minute :-).

...

../../../bin/boost/libs/filesystem/test/path_test.test/gcc/debug/path_test.run ====== BEGIN OUTPUT ====== Platform is POSIX /data2/cgrayson/boost_1_33_1/boost/test/minimal.hpp(122): exception "signal: SIGABRT (application abort requested)" caught in function: 'int main(int, char**)'

**** Testing aborted. **** 1 error detected

EXIT STATUS: 201 ====== END OUTPUT ======

Any chance of getting a call stack trace at time of abort?

The crash is happening when running the "path_test.cpp" test, in particular in the call to "path::default_name_check(fs::no_check);" in the try block below: 77 BOOST_CHECK( path::default_name_check_writable() ); 78 BOOST_CHECK( path::default_name_check() == fs::portable_name ); 79 BOOST_CHECK( !path::default_name_check_writable() ); 80 bool default_name_check_threw = false; 81 try { path::default_name_check( fs::no_check ); } 82 catch ( const fs::filesystem_error & ) { default_name_check_threw = true; } 83 BOOST_CHECK( default_name_check_threw ); Execution never reaches the catch, or the last BOOST_CHECK listed. Thanks, Chris