- Boost-users - lists.preview.boost.org

Using object_pool with a constructor with more that 3 arguments with MSVC
by Pico Geyer 23 Aug '12

23 Aug '12

Hi all. I'm using object pools in some code of mine. The code needs to build on unix (gcc) and on Windows(Visual C++). The objects that I'm constructing take 4 arguments so I needed to use the scripts mentioned in the note on this page: http://www.boost.org/doc/libs/1_51_0/libs/pool/doc/html/boost/object_pool.h… <quote> Since the number and type of arguments to this function is totally arbitrary, a simple system has been set up to automatically generate template construct functions. This system is based on the macro preprocessor m4, which is standard on UNIX systems and also available for Win32 systems. detail/pool_construct.m4, when run with m4, will create the file detail/pool_construct.ipp, which only defines the construct functions for the proper number of arguments. The number of arguments may be passed into the file as an m4 macro, NumberOfArguments; if not provided, it will default to 3. For each different number of arguments (1 to NumberOfArguments), a template function is generated. There are the same number of template parameters as there are arguments, and each argument's type is a reference to that (possibly cv-qualified) template argument. Each possible permutation of the cv-qualifications is also generated. Because each permutation is generated for each possible number of arguments, the included file size grows exponentially in terms of the number of constructor arguments, not linearly. For the sake of rational compile times, only use as many arguments as you need. detail/pool_construct.bat and detail/pool_construct.sh are also provided to call m4, defining NumberOfArguments to be their command-line parameter. See these files for more details." </quote> So I ran this script like so: ./pool_construct.sh 4 And I made sure that Visual C++ is using the right include directory. But I still get the error: error C2660: 'boost::object_pool<T>::construct' : function does not take 4 arguments I then starting digging into the header files to see why pool_construct.ipp is not being included. I then found these two interesting parts in object_pool.hpp: #if defined(BOOST_MSVC) || defined(__KCC) # define BOOST_NO_TEMPLATE_CV_REF_OVERLOADS #endif and #ifndef BOOST_NO_TEMPLATE_CV_REF_OVERLOADS # include <boost/pool/detail/pool_construct.ipp> #else # include <boost/pool/detail/pool_construct_simple.ipp> #endif I don't really understand why the pool_construct_simple.ipp file should instead be included for windows. But if there is a good reason for it, shouldn't the documentation be updated to tell you to instead run the pool_construct_simple.sh script instead? Can anyone provide any information to help me understand this? Thanks in advance. Pico

2 1

boost concept OutputStreamable
by Peter 23 Aug '12

23 Aug '12

Hi, I'm new to the boost concepts library, and I was just wondering if the OutputStreamable concept or similar is available in that library. I couldn't find one. If so, how would I go about writing my own boost concept for that concept? Thanks in advance! Peter

1 0

(no subject)
by Alexandru Geana 23 Aug '12

23 Aug '12

Hello, I am trying to build a boost.log example and I keep getting "undefined references" messages. I searched for how to fix them and came to the conclusion that they are not related to boost.log, but to boost.thread instead. Also, they are coming from a tss.hpp source file found in the boost.thread code. Here is the patebin of the full message: http://pastebin.com/xcsPRVak I am using mingw (gcc 4.7) and boost 1.51 (and codeblocks though I doubt this is relevant). If anyone could please help me I would greatly appreciate it. Best regards, *Alexandru Geana* E-mail address: *alex(a)alegen.net*

2 1

Thread function only called one time. why?
by young 23 Aug '12

23 Aug '12

I have a MFC application which use boost thread. I have created several threads like m_pReadThread / m_pProcessThread / m_pWriteThread m_pProcessThread = boost::shared_ptr<boost::thread>(new boost::thread(boost::bind(&CMFCDlg::ProcessThreadBoost, this))); in each thread, the thread function structure looks like: { init; while(run == true) { // set break point here ... } cleanup code; // set break point here } I set break point When I run my application, one of the thread only reach the first break point once. The second break point never reached. What might be the problem? Since the code is part of a big project. I can not put code here. -- View this message in context: http://boost.2283326.n4.nabble.com/Thread-function-only-called-one-time-why… Sent from the Boost - Users mailing list archive at Nabble.com.

3 2

bjam performance
by Avi Bahra 23 Aug '12

23 Aug '12

I am currently use boost 1.47, does any one know what version of boost includes *any* performance improvements to bjam ? Best regards, Ta, Avi

2 1

[boost::interprocess] assertion failure while buding with -O3
by Priyank Patel 23 Aug '12

23 Aug '12

Hello, I am getting assertion failure in boost inter process library (trying to connect client/server via shared memory). This is happening especially while building an optimized version (-O3). When I build my applications in debug version I do not get this failure. Please let me know if anyone come across this type of issue earlier. I have included stack trace below, also let me know if any more information required. I am using boost version 1_40. #0 0x00007ffff70d1a75 in *__GI_raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x00007ffff70d55c0 in *__GI_abort () at abort.c:92 #2 0x00007ffff70ca941 in *__GI___assert_fail (assertion=0x4888a3 "res == 0", file=<value optimized out>, line=107, function=0x48af60 "void boost::interprocess::interprocess_recursive_mutex::unlock()") at assert.c:81 #3 0x000000000045da9a in void* boost::interprocess::segment_manager<char, boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family, boost::interprocess::offset_ptr<void>, 0ul>, boost::interprocess::iset_index>::priv_generic_find<char>(char const*, boost::interprocess::iset_index<boost::interprocess::detail::index_config<char, boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family, boost::interprocess::offset_ptr<void>, 0ul> > >&, boost::interprocess::detail::in_place_interface&, unsigned long&, boost::interprocess::detail::bool_<true>, bool) () #4 0x000000000043fd88 in priv_find_impl<smpd::State> (this=0x6dc670, clear=<value optimized out>) at /usr/include/boost/interprocess/segment_manager.hpp:704 #5 find<smpd::State> (this=0x6dc670, clear=<value optimized out>) at /usr/include/boost/interprocess/segment_manager.hpp:418 #6 find<smpd::State> (this=0x6dc670, clear=<value optimized out>) at /usr/include/boost/interprocess/detail/managed_memory_impl.hpp:343 #7 find<smpd::State> (this=0x6dc670, clear=<value optimized out>) at /usr/include/boost/interprocess/managed_shared_memory.hpp:197 #8 buildObject<smpd::State> (this=0x6dc670, clear=<value optimized out>) at shm_interface.h:136 Thanks

2 2

1.51 build issue, I think...
by Lemay.Steve 22 Aug '12

22 Aug '12

I am new to building boost, so I apologize if this is an uninformed question. I was able to build the boost 1.49 and 1.50 libraries using qcc 4.4.2 (QNX's gcc 4.4.2) without major issues. Boost 1.51 has added a new wrinkle, and I'm not sure how to address it. Here's a snipit from the build.log. Any help is appreciated. error: No best alternative for libs/context/build/asm_context_sources next alternative: required properties: <abi>aapcs <architecture>arm <binary-format>elf <toolset>gcc not matched next alternative: required properties: <abi>aapcs <architecture>arm <binary-format>elf not matched next alternative: required properties: <abi>o32 <architecture>mips1 <binary-format>elf <toolset>gcc not matched next alternative: required properties: <abi>o32 <architecture>mips1 <binary-format>elf not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>power <binary-format>elf <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>power <binary-format>elf not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>elf <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>elf not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>elf <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>elf <toolset>intel not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>elf not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>mach-o <target-os>darwin <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>mach-o <target-os>darwin <toolset>intel not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>mach-o <target-os>darwin not matched next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <target-os>windows <toolset>intel not matched next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <target-os>windows <toolset>msvc not matched next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <target-os>windows <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>elf <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>elf <toolset>intel not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>elf not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>mach-o <target-os>darwin <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>mach-o <target-os>darwin <toolset>intel not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>mach-o <target-os>darwin not matched next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <target-os>windows <toolset>intel not matched next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <target-os>windows <toolset>msvc not matched next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <target-os>windows <toolset>gcc not matched

4 9

[1.51] PDF documentation build available
by John Maddock 22 Aug '12

22 Aug '12

The PDF build of the docs for 1.51 is now available from: https://sourceforge.net/projects/boost/files/boost-docs/1.51.0/ John.

1 0

boost::pool memory question
by Claude 21 Aug '12

21 Aug '12

Hi! I have tried this program: If I use valgrind obtain this output: It is normal? -- View this message in context: http://boost.2283326.n4.nabble.com/boost-pool-memory-question-tp4634559.html Sent from the Boost - Users mailing list archive at Nabble.com.

4 5

Re: [Boost-users] Boost-users Digest, Vol 3184, Issue 2
by Neil Nelson 21 Aug '12

21 Aug '12

Steve Lemay, gcc 4.4.2 is a bit old now. gcc 4.6 is very common. gcc 4.7 is also available. Neil Nelson > I am new to building boost, so I apologize if this is an uninformed question. I was able to build the boost 1.49 and 1.50 libraries using qcc 4.4.2 (QNX's gcc 4.4.2) without major issues. Boost 1.51 has added a new wrinkle, and I'm not sure how to address it. Here's a snipit from the build.log. Any help is appreciated.

1 0