The test passes, but during program "clean-up", a segmentation violation occurs. Here's the gdb session: GNU gdb 6.3-debian Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-linux"...Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /home/evansl/prog_dev/boost-release/boost_1_32_0/bin.v2/sand-box/lje/libs/fields_visitor/test/gcc/debug/smart_ptr_test Running 13 test cases... *** No errors detected Program received signal SIGSEGV, Segmentation fault. 0x00000011 in ?? () (gdb) bt #0 0x00000011 in ?? () #1 0x08083098 in boost::checked_delete<boost::unit_test::report_formatter> (x=0x80a8c00) at checked_delete.hpp:34 #2 0x0807dc75 in ~scoped_ptr (this=0x80a870c) at scoped_ptr.hpp:77 #3 0x4005339d in __static_initialization_and_destruction_0 (__initialize_p=0, __priority=65535) at ../../../../../libs/test/src/unit_test_result.cpp:297 #4 0x4005343a in global destructors keyed to _ZN5boost9unit_test16unit_test_result4Impl6m_headE () at ../../../../../libs/test/src/unit_test_result.cpp:599 #5 0x400435e0 in __do_global_dtors_aux () from /home/evansl/prog_dev/boost-release/boost_1_32_0/bin.v2/libs/test/build/gcc/debug/boost_unit_test_framework.so #6 0x4005d076 in _fini () from /home/evansl/prog_dev/boost-release/boost_1_32_0/bin.v2/libs/test/build/gcc/debug/boost_unit_test_framework.so #7 0x4000c4f6 in _dl_init () from /lib/ld-linux.so.2 #8 0x4019cae2 in exit () from /lib/libc.so.6 #9 0x40186dce in __libc_start_main () from /lib/libc.so.6 #10 0x08066151 in _start () at ../sysdeps/i386/elf/start.S:102 (gdb) up #1 0x08083098 in boost::checked_delete<boost::unit_test::report_formatter> (x=0x80a8c00) at checked_delete.hpp:34 Anyone else encounter this problem? David or Jonathan, I'll try to narrow the problem down (after all, it may be in the boost_unit_test_framework ), but just thought I'd give others a "heads-up".