Valgrind errors in the boost tests #160
Description
When running the boost tests, valgrind reports lots of errors. The first one is
==221284== Memcheck, a memory error detector
==221284== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al.
==221284== Using Valgrind-3.24.0 and LibVEX; rerun with -h for copyright info
==221284== Command: ./ADOL-C/boost-test/boost-test-adolc
==221284==
==221284== Conditional jump or move depends on uninitialised value(s)
==221284== at 0x49946C0: zos_forward (uni5_for.cpp:1109)
==221284== by 0x11DE71: test_pdouble::ExpOperator_ZOS_Forward::test_method() (pdouble.cpp:46)
==221284== by 0x11D6AE: test_pdouble::ExpOperator_ZOS_Forward_invoker() (pdouble.cpp:24)
==221284== by 0x11BF7C: boost::detail::function::void_function_invoker0<void (*)(), void>::invoke(boost::detail::function::function_buffer&) (function_template.hpp:117)
==221284== by 0x4A43F71: ??? (in /usr/lib/x86_64-linux-gnu/libboost_unit_test_framework.so.1.83.0)
==221284== by 0x4A41BC8: boost::execution_monitor::catch_signals(boost::function<int ()> const&) (in /usr/lib/x86_64-linux-gnu/libboost_unit_test_framework.so.1.83.0)
==221284== by 0x4A41DC2: boost::execution_monitor::execute(boost::function<int ()> const&) (in /usr/lib/x86_64-linux-gnu/libboost_unit_test_framework.so.1.83.0)
==221284== by 0x4A41EA4: boost::execution_monitor::vexecute(boost::function<void ()> const&) (in /usr/lib/x86_64-linux-gnu/libboost_unit_test_framework.so.1.83.0)
==221284== by 0x4A71C74: boost::unit_test::unit_test_monitor_t::execute_and_translate(boost::function<void ()> const&, unsigned long) (in /usr/lib/x86_64-linux-gnu/libboost_unit_test_framework.so.1.83.0)
==221284== by 0x4A496A6: ??? (in /usr/lib/x86_64-linux-gnu/libboost_unit_test_framework.so.1.83.0)
==221284== by 0x4A49A91: ??? (in /usr/lib/x86_64-linux-gnu/libboost_unit_test_framework.so.1.83.0)
==221284== by 0x4A49A91: ??? (in /usr/lib/x86_64-linux-gnu/libboost_unit_test_framework.so.1.83.0)
Can these please be fixed? My own ADOL-C-using code crashes with similar symptoms, and I'm hoping that fixing the tests will also fix my code. Thank you!