- Boost-users - lists.boost.org

[date-time] converting milliseconds to time_duration - overflow issue
by Johan Ditmar 18 May '10

18 May '10

Hello, When I convert a (large) number of milliseconds to a time_duration, I noticed a truncation error. This is shown in the following example: BOOST_AUTO_TEST_CASE(test_time_duration) { static const boost::posix_time::ptime ref(boost::gregorian::date(1400,1,1)); static const boost::posix_time::ptime now(boost::gregorian::date(2010,5,18)); boost::int64_t elapsed = (now-ref).total_milliseconds(); boost::posix_time::time_duration d1 = boost::posix_time::millisec(elapsed); BOOST_CHECK_EQUAL(d1.total_milliseconds(), elapsed); } error in "test_time_duration": check d1.total_milliseconds() == elapsed failed [814839926290 != 19261584000000] This is caused by an overflow issue in the constructor of subsecond_duration (called by boost::posix_time::millisec): template<class base_duration, boost::int64_t frac_of_second> class subsecond_duration : public base_duration { public: typedef typename base_duration::traits_type traits_type; explicit subsecond_duration(boost::int64_t ss) : base_duration(0,0,0,ss*traits_type::res_adjust()/frac_of_second) {} }; Shouldn't this constructor check whether traits_type::res_adjust()>frac_of_second and then do “base_duration(0,0,0,ss*(traits_type::res_adjust()/frac_of_second))” (note the brackets)? Thanks, Johan _________________________________________________________________ http://clk.atdmt.com/UKM/go/195013117/direct/01/

1 0

Boost + Android NDK
by NuSkooler 18 May '10

18 May '10

I've searched the archives quite a bit and haven't run into any answers to this -- if I'm missing something please let me know. I've been working on getting Boost to work with the Android NDK (modified "Crystax" version with RTTI & exceptions) under Cygwin. I now have it working, but what I've come up with seems to be very messy and a couple of the modifications break the standard Linux build. I'm hoping someone can provide pointers to clean this up a bit (and/or this may be useful to anyone out there trying to do the same thing). Step 1: I had to build bjam.exe under Cygwin. This required the following simple patch: --- c:\Unzipped\boost-build\jam_src\expand.c 2007-09-30 23:12:48.000000000 -0600 +++ c:\dev\ghoti\client\external\boost-build\jam_src\expand.c 2010-04-29 14:25:38.322025800 -0600 @@ -749,7 +749,7 @@ assert(l != 0); assert(list_next(l) == 0); # ifdef OS_CYGWIN - assert( !strcmp( l->string, "c:\\foo\\bar" ) ); + //assert( !strcmp( l->string, "c:\\foo\\bar" ) ); # else assert( !strcmp( l->string, cygpath ) ); # endif Step 2: Build Boost under Cygwin against the modified NDK: user-config.jam - Added this entry: # Android ARM Linux Compiler using gcc : arm : /cygdrive/c/dev/ghoti/client/external/android/android-ndk-r3-crystax/build/prebuilt/windows/arm-eabi-4.4.0/bin/arm-eabi-g++ : \ <cxxflags>-I$NDK_ROOT/build/platforms/android-5/arch-arm/usr/include/ \ <cflags>-nostdlib \ <cxxflags>-DBOOST_THREAD_LINUX \ <cxxflags>-DBOOST_HAS_PTHREADS \ <cxxflags>-pthread \ <cxxflags>-D__arm__ \ <cxxflags>-D_REENTRANT \ <cxxflags>-D_GLIBCXX__PTHREADS \ <cxxflags>-DBOOST_HAS_GETTIMEOFDAY \ <cxxflags>-DBOOST_HAS_THREADS \ <cxxflags>-DANDROID \ <cxxflags>--sysroot=$NDK_ROOT/build/platforms/android-5/arch-arm <cxxflags>-D__NEW__ \ <cxxflags>-D__SGI_STL_INTERNAL_PAIR_H \ <cxxflags>-fno-short-enums \ <architecture>arm \ <linkflags>-lc \ <linkflags>-nostdlib \ <linkflags>-Wl,-rpath-link=$NDK_ROOT/build/platforms/android-5/arch-arm/usr/lib/ \ <linkflags>-L$NDK_ROOT/build/platforms/android-5/arch-arm/usr/lib/ \ ; Don't need to link in librt: --- c:\Unzipped\boost_1_42_0\tools\build\v2\tools\gcc.jam 2009-10-28 01:47:51.602868000 -0600 +++ c:\dev\ghoti\client\external\boost_1_42_0\tools\build\v2\tools\gcc.jam 2010-04-30 15:37:39.383973800 -0600 @@ -906,7 +906,8 @@ case * : { option = -pthread ; - libs = rt ; + # BDA: + #libs = rt ; } } ----- --- c:\Unzipped\boost_1_42_0\tools\build\v2\tools\stlport.jam 2009-05-22 05:36:46.841847000 -0600 +++ c:\dev\ghoti\client\external\boost_1_42_0\tools\build\v2\tools\stlport.jam 2010-04-30 15:30:31.864521000 -0600 @@ -198,7 +198,9 @@ # name: stlport_<toolset>(_stldebug)? local name = stlport ; - name = $(name)_$(toolset) ; + # BDA: + #name = $(name)_$(toolset) ; + if [ feature.get-values <runtime-debugging> : $(raw) ] = "on" { name = $(name)_stldebug ; Building: bjam toolset=gcc-arm target-os=linux stdlib=stlport define=_LITTLE_ENDIAN Again, all of this seems very messy. Some of it may not even be necessary. STLPort was something I was messing with; I'm not sure if it's ultimately required (the patch/stdllib=stlport). Any pointers greatly appreciated!

3 2

An error in MTL4(Matrix template Library).Can anyone with kindness help me?
by fmingu 18 May '10

18 May '10

I am using Dev-C++ with gcc 4.4.1 and boost 1.37.0 and MTL 4 (MTLVERSION 4\nMTLRELEASE beta-1\nMTLREVISION 6916 ) for matrix computation. And my code is the following : #define MATRIXCOLS 3 #define MATRIXROWS 3 #include <boost/numeric/mtl/mtl.hpp> using namespace mtl; using namespace mtl::matrix; typedef dense2D<double> Matrix; typedef dense_vector<double> Vec; ................................. using namespace mtl; using namespace mtl::matrix; const unsigned xd= 2, yd= 5, n= xd * yd; Matrix Kk(n,n),Hk(n,n),Rk(n,n);hessian_setup(Kk, 3.0);hessian_setup(Hk, 3.0); Rk=trans(Hk); Vec hxkk_1(n,0.0),zk(n,0.0),hxkk(n,0.0),hxkk_11(n,0.0); hxkk=zk-Hk*hxkk_1; hxkk= Kk*hxkk; //the * line ............................... and it is complied OK. But when it ran to the (*) line the result is : This application has requested the Runtime to terminate it in an unusual way, please contact the application's support team for more information. I found that the mailinglist in http://osl.iu.edu/research/mtl/mtl4/ is quite a place that almost no letters. When I use hxkk*=Kk; instead of the * line,even it can not be complied. So I write letter here for any experts to give me some advices. Can any one with kindness help me?

1 0

Re: [Boost-users] [Asio]Question about error_code when socket::close
by Comet 18 May '10

18 May '10

> BTW, you also can try to use a trivial custom allocator that would > eliminate some heap allocations in completion handlers (unrelated to > shared_ptr): > http://www.boost.org/doc/libs/1_42_0/doc/html/boost_asio/example/allocation… Thanks! that would be very helpful.

1 0

shared_ptr question
by David Michael Bond 18 May '10

18 May '10

Hello, I am learning shared_ptrs and I am running into a segfault. I'm fairly certain it's because of some misunderstanding I have. Here is some code. I have altered it to just so the relevant data: ---- START CODE ---- std::deque<boost::shared_ptr<Frame> > processing_queue ; void this_is_called() { boost::shared_ptr<Frame> rx ; interface->open( "eth0" ) ; while( running ) { interface->rx_frame( this->processing_queue ) ; if( !processing_queue.empty( ) ) { rx = processing_queue.back( ) ; if( rx ) { std::cout << "Received Frame of Ethertype " << ntohs( rx->get_ether_header( ).ether_type ) << "." << std::endl ; } } } } } // rx frame from interface and add onto processing_queue boost::shared_ptr<Frame> last_rx_frame ; // (CLASSXX member) void CLASSXX::rx_frame( std::deque<boost::shared_ptr<Frame> >& processing_queue ) { // Do some stuff to receive frame.. (int size= # bytes in frame) last_rx_frame.reset(new Frame( )) ; last_rx_frame->bytes.reset( new u_char[size]) ; memcpy( last_rx_frame->bytes.get(), frame_bytes, size) ; last_rx_frame->size = size ; processing_queue.push_back( this->last_rx_frame ) ; } ---- END CODE ---- The program receives one frame and successful and outputs it: Received Frame of Ethertype 0x800. But the second time when it gets to 'rx = processing_queue.back( ) ;' I have a segfault. My understanding of shared_ptrs is that when this assignment is done rx will have its ref count decremented (possibly leading to it being deleted). The back of the processing_queue will then become rx do to the assignment and that shared ptrs reference count will be increased by one. Anyone know what my misconception is? Any idea what's causing the segfault? Thanks! -David

1 0

Please help with rebuild on Windows
by John Dlugosz 18 May '10

18 May '10

I want to use the program-options library, and the copy of boost used by this application suite is 1.38. Using Visual Studio 2008, debug build, the resulting program crashes in the variables_map constructor. My assumption is that the compiler options don't match: in particular, a stupid thing called _HAS_ITERATOR_DEBUGGING=0 is infectious as it causes the STL to generate different code and different sized objects. The layout of the boost files doesn't match the documentation, in that bjam.exe is in a subdirectory, and there is no such thing as bootstrap. Anyway, I try: D:\boost_1_38_0> bin\bjam link=static threading=multi variant=debug toolset=msvc-9.0 --define=_HAS_ITERATOR_DEBUGGING=0 Libs\program_options\build and it indeed makes a file with the same name as the one my program is linking to: libboost_program_options-vc90-mt-gd-1_38.lib, which I copy over the original. It made no difference. I don't think that's the specific problem, though, since it crashes on the constructor, not on some later usage from a different translation unit. The call tree is: foo.exe!std::_Tree<std::_Tmap_traits<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,boost::program_options::variable_value,std::less<std::basic_string<char,std::char_traits<char>,std::allocator<char> > >,std::allocator<std::pair<std::basic_string<char,std::char_traits<char>,std::allocator<char> > const ,boost::program_options::variable_value> >,0> >::_Init() Line 1180 + 0xe bytes foo.exe!std::_Tree<std::_Tmap_traits<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,boost::program_options::variable_value,std::less<std::basic_string<char,std::char_traits<char>,std::allocator<char> > >,std::allocator<std::pair<std::basic_string<char,std::char_traits<char>,std::allocator<char> > const ,boost::program_options::variable_value> >,0> >::_Tree<std::_Tmap_traits<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,boost::program_options::variable_value,std::less<std::basic_string<char,std::char_traits<char>,std::allocator<char> > >,std::allocator<std::pair<std::basic_string<char,std::char_traits<char>,std::allocator<char> > const ,boost::program_options::variable_value> >,0> >(const std::less<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > & _Parg=less, const std::allocator<std::pair<std::basic_string<char,std::char_traits<char>,std::allocator<char> > const ,boost::program_options::variable_value> > & _Al={...}) Line 511 foo.exe!std::map<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,boost::program_options::variable_value,std::less<std::basic_string<char,std::char_traits<char>,std::allocator<char> > >,std::allocator<std::pair<std::basic_string<char,std::char_traits<char>,std::allocator<char> > const ,boost::program_options::variable_value> > >::map<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,boost::program_options::variable_value,std::less<std::basic_string<char,std::char_traits<char>,std::allocator<char> > >,std::allocator<std::pair<std::basic_string<char,std::char_traits<char>,std::allocator<char> > const ,boost::program_options::variable_value> > >() Line 104 foo.exe!boost::program_options::variables_map::variables_map() Line 172 + 0x40 bytes foo.exe!main(int argc=1, char * * argv=0x01f84190) Line 179 + 0xb bytes TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and subscription company, and TradeStation Europe Limited, a United Kingdom, FSA-authorized introducing brokerage firm. None of these companies provides trading or investment advice, recommendations or endorsements of any kind. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

3 7

[filesystem] iterator VC 10.0
by Commander Pirx 17 May '10

17 May '10

Hi, I tried to compile the following lines with VC 10: void path_adapter::convert( const boost::filesystem::path& p) { typedef boost::filesystem::path::const_iterator const_path_iterator; for (const_path_iterator pos = p.begin(); pos < p.end(); ++pos) { //... } } and got the error: error C2039: 'distance_to': is not an element of 'boost::filesystem::basic_path<String,Traits>::iterator' Seems to be a problem of the new iterator facade implementation. I had no trouble with this method until Boost 1.43.0. Any idea how to fix this? Pirx!

2 2

BOOST_FIXTURE_TEST_SUITE problem
by Olaf Peter 17 May '10

17 May '10

Hi, the simple snippet doesn't compile on 1.43 or trunk: #include <boost/test/unit_test.hpp> struct F { F() : i( 0 ) { BOOST_TEST_MESSAGE( "setup fixture" ); } ~F() { BOOST_TEST_MESSAGE( "teardown fixture" ); } int i; }; BOOST_FIXTURE_TEST_SUITE( s, F ) $ g++ -I ../boost/1.43/include/ rr.cpp -c rr.cpp:10: error: expected ‘}’ at end of input which results into: ... namespace s { static boost::unit_test::ut_detail::auto_test_unit_registrar s_registrar10( "s" ); typedef F BOOST_AUTO_TEST_CASE_FIXTURE; where the closing '}' is really missing. Does I miss something? Thanks, Olaf

2 1

Re: [Boost-users] Boost-users Digest, Vol 2362, Issue 3
by NuSkooler 17 May '10

17 May '10

> Are you using the trunk's version of STLPort? The STLPort in trunk has > modifications for use in android. Though it assumes it doesn't have RTTI > and exceptions. > You would need to add -D__ANDROID__ as well, since it is this that > STLPort checks for. > I'm still trying to compile and your email was *very* valuable. > Maybe creating a android.jam in the tools/ dir in boost.build would be > better. Glad the post has been helpful -- I probably should have re-tested without the STLPort references. Originally I had been using the standard non-modified NDK and the STLPort from the "ndk-wrappers" posts found on the NDK group. Later I found RTTI and exceptions just too hard to live without and upgraded to the Crystax modified NDK which contains it's own STL (no need for a external STLPort). I'll try re-compiling without any STLPort references now. A android.jam would be great -- So far I've found the jam build system very overwhelming though... I have no clue where to start on something like that. Bryan

1 0

Re: [Boost-users] [Asio]Question about error_code when socket::close
by 鑫炜廖 17 May '10

17 May '10

> Then you need to do reference counting yourself. You must count pending > asynchronous I/O operations and destroy the object when the counter is > decreased to 0. I don't think there is much else you can do? > Boris Thanks, that's a good idea and what I intended to do. Some what ugly, but can be hidden under the table :-)

2 2