- Boost-users - lists.boost.org

program options config file format?
by stark 12 Aug '05

12 Aug '05

Hi About a week ago Mathias Kaepler posted the following question: >Hi, > >the program_options reference talks about being able to parse config >files, but doesn't mention a thing about its layout. No examples are >shown how a file has to look like to be parsable by program_options. > > >Any ideas? Besides the layout, which characters are treated as comments? . > >-- >Matthias Kaeppler I have exactly the same question but have not been able to find the response that was given to Mathias. Would someone share it with me? thanks, Glen Stark

2 1

Re: [Boost-users] Maybe a problem with boost::object_pool?
by Labour, Matthieu (MLPRO SF) 11 Aug '05

11 Aug '05

Caleb Thanks for your answer. I tried running the following program with valgrind but as you said valgrind doesn't complain and I was unable to crash it. Without valgrind sometimes it works fine, sometimes it crashes.... I tested it on 4 different machines. On all of them I had crashes. So I doubt the memory is at fault. Sometimes it requires 20+ threads to crash it. But it crashes always at the same place. Here is an example of simple program + purify trace. I use Red Hat linux 3.2.3-47 Gcc version 3.2.3 20030502 Purify 2003a.05.15 Boost 1.32.0 #include <stdlib.h> #include <iostream> #include <boost/thread/thread.hpp> #include <boost/pool/poolfwd.hpp> #include <boost/pool/object_pool.hpp> class Foo{ public: int foo; }; static boost::object_pool<Foo>* _pool; class Bar{ public: Bar(){} void operator()(){ const int FOO_COUNT = 100; Foo* foo[FOO_COUNT]; int i; for(;;){ for(i=0; i<FOO_COUNT; i++){ try{ foo[i] = _pool->construct(); }catch(...){ std::cout << "exception:construct..." << std::endl; } } for(i=0; i<FOO_COUNT; i++) if (foo[i]){ try{ _pool->destroy(foo[i]); }catch(...){ std::cout << "exception:destroy..." << std::endl; } } } } }; int main(int argc, char* argv[]) { if(argc != 2){ std::cout << "Usage: nbThrd" << std::endl; return 0; } int nbThrd = atoi(argv[1]); _pool = new boost::object_pool<Foo>(10); boost::thread_group _threads; Bar bar; for (int i=0; i<nbThrd; ++i){ _threads.create_thread(bar); } _threads.join_all(); return 0; } **** Purify instrumented custom (pid 23146 at Tue Aug 9 18:13:32 2005) * Purify 2003a.06.15 Linux (32-bit) (c) Copyright IBM Corp. 1992, 2005 All rights reserved. * For contact information type: "purify -help" * For TTY output, use the option "-windows=no" * Command-line: custom 50 * Options settings: -g++=yes -purify -best-effort \ -cache-dir=/home/mlabour/tmp-mlabour-g++ -chain-length=20 \ -fds-inuse-at-exit=no -inuse-at-exit -max_threads=100 \ -purify-home=/tools/rational/2003a.06.15/releases/purify.i386_linux2.200 3a.06.15 \ -gcc3_path=/usr/bin/g++ -cache-dir=/home/mlabour/tmp-mlabour-g++ \ -hw_cap=yes -language=english * License successfully checked out. * Command-line: custom 50 **** Purify instrumented custom (pid 23146) **** MAF: Memory allocation failed (3 times): * This is occurring while in thread 27610032: malloc [rtlib.o] _ZnWjRkSt9nOtHrOw_t [libstdc++.so.5] operator new []( unsigned,std::nothrow_t const &) [libstdc++.so.5] boost::pool<boost::default_user_allocator_new_delete>::ordered_malloc_ne ed_resize( void) [pool.hpp:55] boost::object_pool<Foo,boost::default_user_allocator_new_delete>::constr uct( void) [object_pool.hpp:76] Bar::operator ()( void) [custom.cpp:27] boost::detail::function::void_function_obj_invoker0<Bar, void>::invoke(boost::detail::function::any_pointer) [function_template.hpp:128] boost::function0< void,std::allocator<boost::function_base>>::operator ()( void) const [function_template.hpp:581] thread_proxy [thread.cpp:113] start_thread [libpthread.so.0] clone [libc.so.6] * Attempt to allocate 335544328 bytes failed. **** Purify instrumented custom (pid 23146) **** COR: Fatal core dump: * This is occurring while in thread 1073758112: arena_get2 [libc.so.6] MaLlOc [libc.so.6] _dl_allocate_tls [] allocate_stack [libpthread.so.0] PtHrEaD_CrEaTe@@GlIbC_2.1 [libpthread.so.0] boost::thread::thread(boost::function0< void,std::allocator<boost::function_base>> const &) [thread.cpp:161] boost::thread_group::create_thread(boost::function0< void,std::allocator<boost::function_base>> const &) [thread.cpp:327] main [function_template.hpp:433] __libc_start_main [libc.so.6] _start [crt1.o] * Received signal 11 (SIGSEGV - Segmentation fault) * Handler function: SIG_DFL * Faulting address = 0x40b5e008 * Signal mask: (SIGHUP | SIGQUIT | SIGILL | SIGABRT | SIGBUS | \ SIGKILL | SIGSEGV | SIGALRM | SIGTERM | SIGCHLD | SIGSTOP | SIGSTP | \ SIGTTOU | SIGXFSZ | SIGVTALRM | SIGPWR | SIGUNUSED | SIGReserved35 | \ SIGReserved36 | SIGReserved38 | SIGReserved39 | SIGReserved42 | \ SIGReserved43 | SIGReserved44 | SIGReserved46 | SIGReserved47 | \ SIGReserved53 | SIGReserved54 | SIGReserved57 | SIGReserved58 | \ SIGReserved61 | SIGReserved62) * Pending signals: -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Caleb Epstein Sent: Tuesday, August 09, 2005 8:32 AM To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] Maybe a problem with boost::object_pool? On 8/8/05, Labour, Matthieu (MLPRO SF) <matthieu_labour(a)ml.com> wrote: > A program creates N threads that construct & destroy objects in an > object pool. With N = 9, it crashes on linux That program works fine here with 1, 2, 4, 8, and 9 threads on a 2-way RedHat AS3.1 machine here. I've tried running it with "valgrind" and I don't get any errors. You might try running a memory test on your PC like memtest86. Perhaps you have bad RAM. -- Caleb Epstein caleb dot epstein at gmail dot com _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users -------------------------------------------------------- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ --------------------------------------------------------

2 1

Serialization bug with hash_map?
by Peter Lindman 11 Aug '05

11 Aug '05

Hello, I cannot really get the serializations to work for hash_maps. Using maps, lists and vectors everything works just fine. Using the sample code pasted below (using a hash_map) gives the following compilation-errors: /usr/include/boost/serialization/access.hpp: In static member function `static void boost::serialization::access::serialize(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive, T = __gnu_cxx::hash_map<long int, long int, __gnu_cxx::hash<long int>, std::equal_to<long int>, std::allocator<long int> >]': /usr/include/boost/serialization/serialization.hpp:78: instantiated from `void boost::serialization::serialize(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive, T = __gnu_cxx::hash_map<long int, long int, __gnu_cxx::hash<long int>, std::equal_to<long int>, std::allocator<long int> >]' /usr/include/boost/serialization/serialization.hpp:121: instantiated from `void boost::serialization::serialize_adl(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive, T = __gnu_cxx::hash_map<long int, long int, __gnu_cxx::hash<long int>, std::equal_to<long int>, std::allocator<long int> >]' /usr/include/boost/archive/detail/oserializer.hpp:148: instantiated from `void boost::archive::detail::oserializer<Archive, T>::save_object_data(boost::archive::detail::basic_oarchive&, const void*) const [with Archive = boost::archive::text_oarchive, T = __gnu_cxx::hash_map<long int, long int, __gnu_cxx::hash<long int>, std::equal_to<long int>, std::allocator<long int> >]' /usr/include/boost/archive/detail/oserializer.hpp:243: instantiated from here /usr/include/boost/serialization/access.hpp:106: error: `serialize' undeclared (first use this function) /usr/include/boost/serialization/access.hpp:106: error: (Each undeclared identifier is reported only once for each function it appears in.) Changing the created class to "busmap" (based on std::map) everything works just fine! (The ONLY difference between the classes is the container-definition) System specs: Linux kernel version 2.4.26 g++ (GCC) 3.3.2 20031218 boost-1.32 Sample code compiled with: g++ -o test test.cpp -lboost_serialization-gcc-mt ================================================== #include <fstream> #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/serialization/hash_map.hpp> #include <boost/serialization/map.hpp> #include <ext/hash_map> #include <map> class busmap { friend class boost::serialization::access; std::map<long,long> bus_serial_map; // Imaginary bus-serial-number to bus number lookup-table; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & bus_serial_map; } public: busmap(){} }; class bushashmap { friend class boost::serialization::access; __gnu_cxx::hash_map<long,long> bus_serial_map; // Imaginary bus-serial-number to bus number lookup-table; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & bus_serial_map; } public: bushashmap(){} }; int main() { // create and open a character archive for output std::ofstream ofs("filename"); boost::archive::text_oarchive oa(ofs); // create class instance const bushashmap myBusMap; // write class instance to archive oa << myBusMap; // close archive ofs.close(); // ... some time later restore the class instance to its orginal state // create and open an archive for input std::ifstream ifs("filename", std::ios::binary); boost::archive::text_iarchive ia(ifs); // read class state from archive busmap myNewBusMap; ia >> myNewBusMap; // close archive ifs.close(); return 0; } ======================================= Bug or my fault?? Can anyone help? Best regards Peter

4 4

how to wait for a thread until it stopped
by Christian Henning 11 Aug '05

11 Aug '05

Hi there, I'm still working on the transistion from an old thread lib to the boost thread lib. I have two threads, the GUI thread and a worker thread. The worker thread is always inside a loop that only breaks if someone set the flag. The GUI thread has from time to time to stop the worker thread. This is currently done by setting a flag ( _bStop ) and the worker thread will eventually stop like: void run() { boost::mutex::scoped_lock oLock( _oRunMutex ); do { ... if( _bStop ) _oRunCondition.wait( oLock ); } while( _bTerminate == false ); } I believe that this implemention can lead to deadlocks. But how can I implement the behavior that the GUI thread will break until the worker thread has stopped. Thanks, Christian

4 7

MSVC .NET and boost 1.33 serialization error (Compiler Limit)
by Shawn McCool 11 Aug '05

11 Aug '05

Hi, I'm using MSVC .NET (7.1). Your site says that Visual Studio 6's compiler won't compile boost serialization code because of a "Compiler Limit". The site also says that VS 7.1 has no known problems. I'm getting that exact compiler error. Is this a know issue? ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs

4 3

Regex: option for case insensitive match
by Kiran Reddy 11 Aug '05

11 Aug '05

Hello, I need to make an case insensitive match using regex_match() algorithm. How do I specify that? Thanks in advance. Regards Kiran

3 2

boost::test in 1.33
by Serge Skorokhodov 11 Aug '05

11 Aug '05

Hi, What happend with boost::unit_test::register_exception_translator? I couldn't track it in the boost 1.33:( How to register custom exceptions? The documentation provides no hints:( TIA -- Serge

2 7

problems using overloaded output operator with program_optoins::optoins_description in debug mode vc++ 7.1
by stark 11 Aug '05

11 Aug '05

Hi I'm trying to use the program_options header to satisfy my command line needs, and I have have run into the following quirk with boost version 1.32 and microsoft visual c++ 7.1 when trying to use 'cout<<' to output the program_options::options_description. Appartently there is a limit to the length of the program option name. When not specifying short optoins names, the option name seems to be limited to 12 characters. greater than this and I get a debug assertion failure in dbgheap.c line 1132 expression: _CrtIsValidHeapPointer(pUserData) . When specifying a short option name, the limit for the full name seems to be 6 characters. More than this results in a debug assertion falure in debug mode (msvc++ 7.1, file dbgdel.cpp, line 52) _BLOCK_TYPE_IS_VALID(pHead->nBlockUse). Is there something I can do to to fix this or work around the problem (besides restricting the length of my option names)? Is this a compiler specific problem? Something wrong with my settings? many thanks, Glen Stark

2 1

Prombles compiling 1.33 RC1 with Intel C++ 8.1 on Windows XP
by Sean Huang 11 Aug '05

11 Aug '05

BlankI'm having problems compiling signals library 1.33 RC1 with Intel C++ 8.1. Looks like it only happens when building dll version of signals library. Eveything else compiles fine. It also compiles with VC7.1. I have set the following environment variables: set TOOLS=intel-win32-8_1 set INTEL_BASE_MSVC_TOOLSET=vc-7_1 set INTEL_PATH="c:\Program Files\Intel\CPP\Compiler80\Ia32" set INTEL_VERSION=8.1 The command line I use is bjam "--builddir=D:\Boost_Build\1_33_0" stage. The intel compiler version is: W_CC_PC_8.1.030 I got error messages like the following: vc-C++ D:\Boost_Build\1_33_0\bin\boost\libs\signals\build\boost_signals.dll\intel-win32-8_1\debug\threading-multi\named_slot_map.obj named_slot_map.cpp C:\Program Files\boost_1_33_0\boost/iterator/iterator_facade.hpp(529): error: class "boost::signals::detail::named_slot_map_iterator" has no member "decrement" f.decrement(); ^ detected during: instantiation of "void boost::iterator_core_access::decrement(Facade &) [with Facade=boost::signals::detail::named_slot_map_iterator]" at line 682 instantiation of "Derived &boost::iterator_facade<Derived, Value, CategoryOrTraversal, Reference, Difference>::operator--() [with Derived=boost::signals::detail::named_slot_map_iterator, Value=boost::signals::detail::connection_slot_pair, CategoryOrTraversal=boost::forward_traversal_tag, Reference=boost::signals::detail::connection_slot_pair &, Difference=ptrdiff_t={int}]" C:\Program Files\boost_1_33_0\boost/iterator/iterator_facade.hpp(547): error: class "boost::signals::detail::named_slot_map_iterator" has no member "advance" f.advance(n); ^ detected during: instantiation of "void boost::iterator_core_access::advance(Facade &, Facade::difference_type) [with Facade=boost::signals::detail::named_slot_map_iterator]" at line 695 instantiation of "Derived &boost::iterator_facade<Derived, Value, CategoryOrTraversal, Reference, Difference>::operator+=(boost::iterator_facade<Derived, Value, CategoryOrTraversal, Reference, Difference>::difference_type) [with Derived=boost::signals::detail::named_slot_map_iterator, Value=boost::signals::detail::connection_slot_pair, CategoryOrTraversal=boost::forward_traversal_tag, Reference=boost::signals::detail::connection_slot_pair &, Difference=ptrdiff_t={int}]" CALL "c:\Program Files\Intel\CPP\Compiler80\Ia32\bin\ICLVARS.BAT" > nul "c:\Program Files\Intel\CPP\Compiler80\Ia32\bin\icl" /Zm800 -nologo /EHsc -c -DBOOST_SIGNALS_DYN_LINK=1 -DBOOST_SIGNALS_NO_LIB=1 /Z7 /Od /Ob0 /EHsc /GR /MDd /Op /DBOOST_ALL_NO_LIB=1 /wd4675 /Zc:forScope /Zc:wchar_t /Qwn5 /Qwd985 /Qwe556 -Qoption,c,--arg_dep_lookup /Qansi_alias /Qvc7.1 -D_NATIVE_WCHAR_T_DEFINED -I"D:\Boost_Build\1_33_0\bin\boost\libs\signals\build" -I"C:\Program les\boost_1_33_0" -Fo"D:\Boost_Build\1_33_0\bin\boost\libs\signals\build\boost_signals.dll\intel-win32-8_1\debug\threading-multi\named_slot_map.obj" -Tp"C:\Program Files\boost_1_33_0\libs\signals\build\../src/named_slot_map.cpp" ..failed vc-C++ D:\Boost_Build\1_33_0\bin\boost\libs\signals\build\boost_signals.dll\intel-win32-8_1\debug\threading-multi\named_slot_map.obj...

4 8

tribool question
by Serge Skorokhodov 11 Aug '05

11 Aug '05

Hi, I'm using boost::logic::tribool for expressing logical flags that may be nulls by their nature (patient not asked, he/she doesn't know etc.). Default initialization to 'false' seems to be quite unnatural in this context and initialization to 'undetermined' seems to be prefered. Is any significant reason for boost::logic::tribool default constructor initializing the value to 'false'? TIA -- Serge

7 12