On 04/11/2012 10:47 AM, Alan Conway wrote:
Suddenly unit_test has started to crash on exit for me. Is anyone else having
problems?
Its a seg fault after all the tests have run, in static destructors for the
boost library:
#0 0x0000003e0807a5ac in free () from /lib64/libc.so.6
#1 0x00000036896671ac in clear (this=0x36898bd620, __in_chrg=<value optimized
out>)
at /usr/src/debug/boost-1.41.0.cmake0/boost/test/impl/framework.ipp:133
#2 boost::unit_test::framework_impl::~framework_impl (this=0x36898bd620,
__in_chrg=<value optimized out>)
at /usr/src/debug/boost-1.41.0.cmake0/boost/test/impl/framework.ipp:122
#3 0x0000003e08035d92 in exit () from /lib64/libc.so.6
#4 0x0000003e0801ece4 in __libc_start_main () from /lib64/libc.so.6
#5 0x0000000000402c29 in _start ()
I'm pretty sure I've seen something like this before but I don't remember the
cure. Anybody have an idea?
Now I remember: this happens on some versions of boost if you set MALLOC_PRETUB_
in your environment. MALLOC_PRETURB_ tells malloc to write over all deleted
memory with a byte of your choosing, it catches some memory errors and makes it
easy to see if some code is using deleted memory. Its exposing a bug in the
boost test framework.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
