- Boost-users - lists.boost.org

numeric/interval overflow & test_float failures
by Steven Solie 11 Aug '05

11 Aug '05

I really don't understand the following math library test failures (Boost 1.32.0): 1) test_float.output /Code/boost-os4/libs/numeric/interval/test/test_float.cpp(55): fatal error in "call_test_main": test subset(rIT2, rII) failed 2) overflow.output /Code/boost-os4/libs/numeric/interval/test/overflow.cpp(22): test in(x, y) failed in function: 'void test_one(typename I::base_type, typename I::base_type) [with I = boost::numeric::interval<float, boost::numeric::interval_lib::policies<boost::numeric::interval_lib::rounded_math<float>, boost::numeric::interval_lib::checking_strict<float> > >]' /Code/boost-os4/libs/numeric/interval/test/overflow.cpp(22): test in(x, y) failed in function: 'void test_one(typename I::base_type, typename I::base_type) [with I = boost::numeric::interval<long double, boost::numeric::interval_lib::policies<boost::numeric::interval_lib::rounded_math<long double>, boost::numeric::interval_lib::checking_strict<long double> > >]' I'm using GCC 3.4.4 on AmigaOS PowerPC. First, what do these errors mean in English? Second, any ideas what I could do to get them to pass? Thanks, --Steven

2 1

shared_ptr conundrum
by Timothy Ritchey 11 Aug '05

11 Aug '05

We have been using shared_ptrs pretty successfully throughout our application, but I have run across something that has just completely stumped me. BTW - this is a Windows .NET 2003 + Intel 8.1 compiler compiling in Debug mode on a multi-processor machine (dual Xeon Dell workstation). The code in question is: void Router::routeEnvelope(shared_ptr<Envelope> envelope) { if(!running || !envelope) return; GUID target = envelope->getTo(); if(target == guid) { // PATH 1 // check to see if it is a failure envelope shared_ptr<EnvelopeFailure> envelopeFailure = shared_dynamic_cast<EnvelopeFailure>(envelope); if(envelopeFailure) { // there was a problem sending the original envelope failedEnvelope(envelopeFailure->getFrom()); } // pass it on up the stack envelopeController.injectEnvelope(envelope); } else { // PATH 2 mutex::scoped_lock lock(envelopeQueueMonitor); envelopeQueue.push(envelope); envelopeReady.notify_all(); } } The first envelope that comes in has a guid that matches target, so it takes code path 1. If I comment out both code path 1 and code path 2, the envelope is released properly, and I can see its destructor get called. Here is where it gets strange--if I uncomment anything in code path 2, and only code path 2, I no longer see the envelope get released, even though that code path is not executed at all. I've been doing this testing on an SMP machine. On a UP machine, the program runs fine without any issues. I am at a complete loss. The original envelope object is created in the function that calls this function, and as far as I can tell , is not touched by any other thread in the application. Thanks for any advice. Cheers, tim

2 2

archive stuck?
by Gennadiy Rozental 11 Aug '05

11 Aug '05

I don't see this month messages here: http://lists.boost.org/boost/2005/08/date.php Gennadiy

1 0

Boost 1.33.0 RC2: VS 8.0 / AMD64 Build Patch
by p.klotz＠icoserve.com 10 Aug '05

10 Aug '05

The attached patch fixes a bug in the vc-8_0-amd64 Toolset of Boost 1.33.0 RC2. Best regards, Peter.

3 2

Boost 1.33.0 RC2: Boost.Threads does not link under VC 8.0/AMD64
by p.klotz＠icoserve.com 10 Aug '05

10 Aug '05

Hi Linking of Boost.Threads (Boost 1.33.0 RC2) fails under VC 8.0/AMD64 with the following error: vc-C++ bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-multi\xtime.obj xtime.cpp vc-Link bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-multi\boost_thread-vc80-mt-gd-1_33.dll bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-multi\boost_thread-vc80-mt-gd-1_33.lib Creating library bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-multi\boost_thread-vc80-mt -gd-1_33.lib and object bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-multi\boost_thread-vc8 0-mt-gd-1_33.exp once.obj : error LNK2019: unresolved external symbol _InterlockedCompareExchange referenced in function "long __cdecl `a nonymous namespace'::compare_exchange(long * volatile,long,long)" (?compare_exchange@?A0x083100d6@@YAJREAJJJ@Z) bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-multi\boost_thread-vc80-mt-gd-1_33.dll : fatal error LNK1120: 1 unresolved externals Microsoft (R) Manifest Tool version 6.0.4071.0 Copyright (c) Microsoft Corporation 2004. All rights reserved. mt.exe:general error c101008d:Failed to write the updated manifest to the resource of file "bin\boost\libs\thread\build\ boost_thread.dll\vc-8_0-amd64\debug\threading-multi\boost_thread-vc80-mt-gd-1_33.dll". The system cannot find the file s pecified. CALL "C:\Program Files (x86)\Microsoft Visual Studio 8\Common7\Tools\..\..\VC\bin\amd64\vcvarsamd64.BAT" >nul "C:\Program Files (x86)\Microsoft Visual Studio 8\Common7\Tools\..\..\VC\bin\amd64\link" /nologo /INCREMENTAL:NO / DEBUG /DLL /subsystem:console /out:"bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-multi\bo ost_thread-vc80-mt-gd-1_33.dll" /IMPLIB:"bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-mult i\boost_thread-vc80-mt-gd-1_33.lib" @"bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-mult i\boost_thread-vc80-mt-gd-1_33.CMD" mt -manifest bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-multi\boost_thread-vc80-mt-gd -1_33.dll.manifest -outputresource:bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-multi\boos t_thread-vc80-mt-gd-1_33.dll;#2 ...failed vc-Link bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-multi\boost_thread-vc80-mt-g d-1_33.dll bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-multi\boost_thread-vc80-mt-gd-1_33. lib... ...failed updating 1 target... ...updated 682 targets... Any help is welcome. Best regards, Peter.

1 0

Re: [Boost-users] logical_and, boost::bind, and boost::function
by Simmons, Aaron 10 Aug '05

10 Aug '05

>Alan's post made me realize what's happening. Indeed, this last bind() >doesn't know that funcFoo and funcBar are functions that it should >call. You can tell it to consider them as functions by calling bind() >on them: Rather than wrapping another bind around them, is it possible to do some kind of clever casting, so that bind wouldn't see them as booleans? Btw, is the way I'm using function and bind not an intended use case? It seems natural enough, but by its behavior perhaps no one thought about it before... Thanks, aaron

2 1

A error occurs when compiling the wave
by 沈慧峰 10 Aug '05

10 Aug '05

Hi, respected boost maintainers. I compile the boost_1_33_0_rc2 with vc7.1 with stlport 4.62, my cl version is 13.10.3077. I compile the stlport with /Zc:wchar_t, so I change <native-wchar_t>on when compiling. Here is my script to compile boost 1.33 ------------------------------------------------------- call "c:\Program Files\Microsoft Visual Studio .NET 2003\vc7\bin\vcvars32.bat" set BOOST_ROOT=c:\temp\boost set PYTHON_ROOT=c:\python set PYTHON_VERSION=2.4 set STLPORT_PATH=c:\temp set STLPORT_4.62_PATH=C:\temp\STLport-4.6.2 set STLPORT_VERSION=4.6.2 set TOOLS=vc-7_1-stlport bjam "-sBUILD=<native-wchar_t>on" install ------------------------------------------------------- A error occur when compile instantiate_cpp_grammar.cpp. The whole error message is : "cl" /Zm800 -nologo /EHsc -c -D_STLP_DEBUG=1 -D_STLP_DEBUG_UNINITIALIZED=1 -D_STLP_USE_DYNAMIC_LIB=1 /Z7 /Od /Ob0 /EHsc /GR /MDd /Op /wd4675 /Zc:forScope Zc:wchar_t -I"bin\boost\libs\wave\build" -I"C:\temp\boost_1_33_0" -I"c:\temp\STLport-4.6.2\stlport" -I"C:\temp\boost_1_33_0" -Fo"bin\boost\libs\wave\build\libboost_wave.lib\vc-7_1-stlport\debug\native-wchar_t-on\threading-multi\instantiate_cpp_grammar.obj" -Tp"C:\temp\boost_1_33_0\libs\wave\build\../src/instantiate_cpp_grammar.cpp" ...failed vc-C++ bin\boost\libs\wave\build\libboost_wave.lib\vc-7_1-stlport\debug\native-wchar_t-on\threading-multi\instantiate_cpp_grammar.obj... ...skipped <@boost!libs!wave!build\libboost_wave.lib\vc-7_1-stlport\debug\native-wchar_t-on\threading-multi>libboost_wave-vc71-mt-gdp-1_33.CMD for lack of <@boost!libs!wave!build\libboost_wave.lib\vc-7_1-stlport\debug\native-wchar_t-on\threading-multi>instantiate_cpp_grammar.obj... ...skipped <@boost!libs!wave!build\libboost_wave.lib\vc-7_1-stlport\debug\native-wchar_t-on\threading-multi>libboost_wave-vc71-mt-gdp-1_33.lib for lack of <@boost!libs!wave!build\libboost_wave.lib\vc-7_1-stlport\debug\native-wchar_t-on\threading-multi>instantiate_cpp_grammar.obj... ...skipped <@boost!lib>libboost_wave-vc71-mt-gdp-1_33.lib for lack of <@boost!libs!wave!build\libboost_wave.lib\vc-7_1-stlport\debug\native-wchar_t-on\threading-multi>libboost_wave-vc71-mt-gdp-1_33.lib... I do not know whether the attachment can be paste, the attachment is the scapture of the error. I also try bjam "-sBUILD=debug release <runtime-link>static/dynamic <threading>single/multi <native-wchar_t>on" install The same error occurs three times. Best regards Huifeng Shen

3 2

[Thread] How to wait for a thread until it's blocked
by Christian Henning 10 Aug '05

10 Aug '05

Hi there, seems the attention span for my last question is over. ;-) I also think that my subject was misleading. My question isn't about terminating, completing, or canceling a thread. It's about putting a thread in a blocked state. Please consider the following code. All functions, except for the run(), are called by the GUI thread. The _oThread object is RAII-object ( Resource Allocation is Initialization ). // Only called by GUI thread fvAsynchronousSequencer::fvAsynchronousSequencer() : _oThread ( ) , _bTerminateSequencerThread ( false ) , _bStop( false ) { _oThread.create( this, _run ); } // Only called by GUI thread fvAsynchronousSequencer::~fvAsynchronousSequencer() throw() { _bTerminateSequencerThread = true; // wake up the thread, if necessary _oRunCondition.notify_one(); // wait until the thread is terminated { boost::mutex::scoped_lock oLock( _oTerminateMutex ); _oTerminateCond.wait( oLock ); } } // Only called by GUI thread void fvAsynchronousSequencer::start() { _bStop = false; _oRunCondition.notify_one(); } // Only called by GUI thread void fvAsynchronousSequencer::stop() throw() { _bStop = true; // I would like to wait until the _oThread is a in blocked position. } void fvAsynchronousSequencer::_run() throw() { boost::mutex::scoped_lock oLock( _oRunMutex ); // Wait until someone calls start() _oRunCondition.wait( oLock ); do { // do something useful while( _bStop ) _oRunCondition.wait( oLock ); } while( !_bTerminateSequencerThread ); // now finish destructing the sequencer _oTerminateCond.notify_one(); } So, I will ask again my question. Is there a way that the stop() will only return when the worker thread in in blocked state? Right now, I just set _bStop to true and stop() returns. This approach is of course rife for deadlocks. Thanks again, Christian

1 0

logical_and, boost::bind, and boost::function
by Simmons, Aaron 10 Aug '05

10 Aug '05

I'm trying to use boost::bind and boost::function with std::logical_not and I've run into some strange template magic that I don't understand. In the example below, I use boost::function to help compose several boost::bind calls so that I don't have to do it all on one line (I find that this improves readability). The problem is that when I do this, the functions that are bound with boost::bind never get called. They will get called only if I construct everything on one line. (???) Is this expected behavior? If so, why does it work like this? Thanks, aaron #include <algorithm> #include <functional> #include "boost/bind.hpp" #include "boost/function.hpp" using namespace std; using namespace boost; class test { public: void bindtest() { // test1: composed gradually for clarity // function<bool ()> funcFoo = bind(&test::foo, this); function<bool ()> funcBar = bind(&test::bar, this); function<bool ()> funcTest1= bind(logical_and<bool>(), funcFoo, funcBar); // doesn't call test::foo or test::bar! (returns true) bool test1= funcTest1(); cout << "test1= " << test1 << endl; // test2: composed directly on one line function<bool ()> funcTest2= bind(logical_and<bool>(), bind(&test::foo, this), bind(&test::bar, this) ); // calls test::foo and test::bar (returns false) bool test2= funcTest2(); cout << "test2= " << test2 << endl; } bool foo() { cout << "foo" << endl; return false; } bool bar() { cout << "bar" << endl; return false; } };

2 1

Re: [Boost-users] logical_and, boost::bind, and boost::function
by Alan M. Carroll 10 Aug '05

10 Aug '05

1 0