- Boost - lists.preview.boost.org

How to center an element in Boost QuickBook?
by Niall Douglas 10 Oct '13

10 Oct '13

As the documentation for proposed Boost.AFIO comes together for this week's GSoC Milestone 1 (feel free to check it out at https://ci.nedprod.com/job/Boost.AFIO%20Build%20Documentation/Boost.AFIO_Doc umentation/?), a problem has emerged. We'd like a matrix table containing ticks and crosses, and building such a thing in QuickBook is easy. However, we'd also like to center the ticks and crosses in each table cell, otherwise it looks poor. Is there some way I haven't realized of aligning content in Boost QuickBook, or even BoostBook itself? The DocBook documentation suggests one can do a '''<entry align="center">'''__tick__'''</entry>''' (the triple single ticks escape from QuickBook into BoostBook). However unfortunately BoostBook defines CSS which overrides the per-cell alignment :( Thanks in advance for the help. Niall --- Opinions expressed here are my own and do not necessarily represent those of BlackBerry Inc.

9 22

Try out a multi-dimensional adapter class template?
by Daryle Walker 10 Oct '13

10 Oct '13

I added a new class template for my library at <https://github.com/CTMacUser/ArrayMD>. It's called "multiarray," and it's an adapter class like stack and queue. But the new interface is only for accessing elements. Besides the element and container types, the template header for the class takes the number of dimensions. The class uses at, operator [] and operator () to access an element. It has methods to read/write the shape of the array and the priority of each index. There are no methods to change the number of elements stored; you have to either use a fixed-size container or sub-class the multi-array to add methods to change the size. (The container sub-object is protected, like the Standard adapters.) I split the main code into two base class templates, because the code for computing the offset from an index tuple and the code for referencing an element were nearly distinct. This really screws up my attempt at Doxygen comments. Any ideas? Or is my case too complex for what Doxygen's author thought could be handled. Daryle W.

5 9

[tokenizer] Some remarks
by Robert Kawulak 09 Oct '13

09 Oct '13

Hi, I have a few proposals/questions related to boost::tokenizer: - the first template parameter of char_separator and other tokenizer functions could be defaulted to char to save typing and make it consistent with the defaults of tokenizer; - making the constructor of char_separator and other tokenizer functions non-explicit would allow for less verbose construction of a tokenizer; - the docs state that char_delimiters_separator is deprecated in favour of char_separator. Are there any plans to actually drop the former and change the default for the template parameter of tokenizer to the latter? I guess this might be controversial because interfaces and semantics of the two differ, so maybe providing a new template, say string_tokenizer, is a good idea? Combining the first two points, the following: auto t = boost::tokenizer<boost::char_separator<char>>( str, boost::char_separator<char>("-;|")); could be written more conveniently as: auto t = boost::tokenizer<boost::char_separator<>>(str, "-;|"); and adding the third point it would become: auto t = boost::string_tokenizer<>(str, "-;|"); which is IMO a significant improvement. Any thoughts? Best regards, Robert

1 0

[any] Infinite loop in boost::any in boost release 1.54.0 using Visual C++ 2010
by Bo Peng 09 Oct '13

09 Oct '13

This very simple code: #include <boost/any.hpp> #include <string> const boost::any getBoolVal() { return false; } int main() { boost::any vals[] = {1.0, std::string("1m"), getBoolVal()}; } When built using Visual C++ 2010, it will run into a infinite loop: ntdll.dll!_RtlAllocateHeap@12() + 0x8 bytes ntdll.dll!_RtlDebugAllocateHeap@12() + 0x86 bytes ntdll.dll!@RtlpAllocateHeap@20() + 0x1108a bytes ntdll.dll!_RtlAllocateHeap@12() - 0x28d8a bytes msvcr100d.dll!_heap_alloc_base(unsigned int size=44) Line 55 C msvcr100d.dll!_heap_alloc_dbg_impl(unsigned int nSize=8, int nBlockUse=1, const char * szFileName=0x00000000, int nLine=0, int * errno_tmp=0x002a3280) Line 431 + 0x9 bytes C++ msvcr100d.dll!_nh_malloc_dbg_impl(unsigned int nSize=8, int nhFlag=0, int nBlockUse=1, const char * szFileName=0x00000000, int nLine=0, int * errno_tmp=0x002a3280) Line 239 + 0x19 bytes C++ msvcr100d.dll!_nh_malloc_dbg(unsigned int nSize=8, int nhFlag=0, int nBlockUse=1, const char * szFileName=0x00000000, int nLine=0) Line 302 + 0x1d bytes C++ msvcr100d.dll!malloc(unsigned int nSize=8) Line 56 + 0x15 bytes C++ msvcr100d.dll!operator new(unsigned int size=8) Line 59 + 0x9 bytes C++ test.exe!boost::any::any<boost::any const >(const boost::any && value={...}, void * __formal=0x00000000) Line 73 + 0x49 bytes C++ test.exe!boost::any::holder<boost::any const >::holder<boost::any const >(const boost::any && value={...}) Line 177 C++ ... test.exe!boost::any::any<boost::any const >(const boost::any && value={...}, void * __formal=0x00000000) Line 73 + 0x71 bytes C++ test.exe!boost::any::holder<boost::any const >::holder<boost::any const >(const boost::any && value={...}) Line 177 C++ test.exe!boost::any::any<boost::any const >(const boost::any && value={...}, void * __formal=0x00000000) Line 73 + 0x71 bytes C++ test.exe!boost::any::holder<boost::any const >::holder<boost::any const >(const boost::any && value={...}) Line 177 C++ test.exe!boost::any::any<boost::any const >(const boost::any && value={...}, void * __formal=0x00000000) Line 73 + 0x71 bytes C++ test.exe!boost::any::holder<boost::any const >::holder<boost::any const >(const boost::any && value={...}) Line 177 C++ > test.exe!boost::any::any<boost::any const >(const boost::any && value={...}, void * __formal=0x00000000) Line 73 + 0x71 bytes C++ test.exe!main() Line 11 + 0x9c bytes C++ Sorry I don't know enough of the c++ standard to figure out whether it is because of Visual C++ or it is because of boost. But I think it is worth to raise it to the experts out here. Thanks Bo ---- http://www.pengbo.me

3 3

[Boost.extension] Current Status
by Sean Farrow 08 Oct '13

08 Oct '13

Hi, Does anybody know what the current status of the boost.extension library is, it's not been updated since 2008. Any help appreciated. Regards Sean.

2 1

[website][getting started] Linking to binaries
by Daniel James 08 Oct '13

08 Oct '13

On 8 October 2013 15:58, Tom Kent <lists(a)teeks99.com> wrote: > > The corresponding windows binaries for msvc-8.0, msvc-9.0, msvc-10.0, and > msvc-11.0 in 32 & 64 bit versions are now also available from sourceforge. > > https://sourceforge.net/projects/boost/files/boost-binaries/1.55.0_beta1/ We should probably link to binaries from the website somewhere. If not in the release notes, maybe there should be some information about alternative downloads on the download page. Any opinions? Also for other platforms? (e.g. debian packages). The getting started guide used to mention the old binaries, you can see what was removed at: https://svn.boost.org/trac/boost/changeset/82893/trunk/more/getting_started… We could put back something like that. Especially if anyone fancies writing it? I don't use windows much so I'm not the best person.

1 0

[graph] porting code from 1.46 to 1.54
by Maurizio Vitale 08 Oct '13

08 Oct '13

Hello boost, I'm trying to move some large code base to use boost 1.54. In some dark corner of it, the following was compiling fine: class Instance; typedef boost::setS OutEdgeList; typedef boost::listS VertexList; struct InstancePropertyTag { typedef boost::vertex_property_tag kind; }; typedef boost::property<InstancePropertyTag, Instance*> InstanceProperty; typedef boost::adjacency_list<OutEdgeList, VertexList, boost::bidirectionalS, InstanceProperty> Graph; typedef boost::property_map<Graph, boost::vertex_index_t>::type IndexGraph; under 1.54, I get 'attempt to form reference to void', but everything was fine under 1.46. I traced it a bit through template expansion, and the problem seems to be that the type for vertex_index_t is not found. The following declaration for InstanceProperty fixes (or hides) the problem: typedef boost::property<InstancePropertyTag, Instance*, boost::property<boost::vertex_index_t, int> > InstanceProperty; Does somebody know if some properties were added by default to graphs before and need to be explicitly added now? I don't find anything in the documentation and all examples I've found seem to imply that one wouldn't need to explicitly add a property declaration of vertex_index_t. Thanks a lot, Maurizio

3 4

[1.55.0] Release branch now open
by Marshall Clow 08 Oct '13

08 Oct '13

The release branch is now open for bug fixes and doc updates, without need to ask for a release manager's permission. It will remain open until Monday, October 28th. The 1.55.0 release is scheduled for November 4th. -- Marshall

1 0

[1.55.0] Release Notes
by Daniel James 08 Oct '13

08 Oct '13

Hello, If you haven't already, can you write your release notes for 1.55? You can send them to me, or add them yourself at: http://svn.boost.org/svn/boost/website/public_html/live/feed/history/ They're on the website at: http://www.boost.org/users/history/version_1_55_0.html thanks, Daniel

12 24

Boost.Application : Request for comments : Article / Thread Pool / Other Features / Documentation
by Renato Forti 08 Oct '13

08 Oct '13

Hi All, In this email I would like to discuss some areas of Boost.Application. 01) Thread Pool functionality One of the most recurring requests is that Boost.Application should provide Thread Pool functionality. A flexible Thread Pool can be a complex thing, need provide schedule polices, grow/reduce polices, Shutdown policies, deadline s and many others, and then I think that this feature devotes your own Boost library. The Boost.Application can be integrated easily with one Thread Pool provided by third parties, or the user can make one "specific" (Not flexible/Complex) to your needs, e.g.: I make a simple work queue model using Boost.Asio and Boost.Thread that I plug on Boost.Application, see these tutorial: * Creating a Work Queue (Thread Pool) Application Using Boost.Asio, Boost.Thread and Boost.Application http://www.codeproject.com/Articles/664709/Creating-a-Work-Queue-Thread-Pool -Application-Usin My question is: The boost users think that Boost.Application must provide a complex Thread Pool to be accepted? 02) Ideas (new features) So far these are the ideas proposed to improve Boost.Application: http://www.dokfile.com/appbeta3/docs/libs/application/doc/html/application/f uture.html What functionality do you think should already be included in the first release, and not only in future versions? (Please mention here!) If you have any other ideas, (or improvement of current list) please post here so that I can update the "TODO" session. 03) Articles About "Boost.Application" I published other articles about "Boost.Application" on Code Project Website. Code Project Tutorials * Create a Windows Service Application http://www.codeproject.com/Articles/662221/Create-a-Windows-Service-Applicat ion-Using-the-Boo 04) Documentation Feedback Also, the library documentation was updated. If someone can take a look! Please, tell me if this is a little more understandable. * On-Line Documentation http://www.dokfile.com/appbeta3/docs/libs/application/doc/html/index.html 05) Boost.Application Resources [Other Boost.Application Resources] * Download Last Version https://sourceforge.net/projects/boostapp/ Note that the latest version is (10/07/2013): Boost.Application_beta_3a_release_5.zip (1.4 MB) * Please Write a Review https://sourceforge.net/projects/boostapp/reviews Please send comments. (Specify if you think if the library should be accepted as part of boost) Thank you very much! -- Renato

4 6

1.55.0 beta 1 release candidates available for testing
by Marshall Clow 08 Oct '13

08 Oct '13

Release candidate files for 1.55.0 beta 1 are available at http://boost.cowic.de/rc/ As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. This helps ensure the candidates build OK before we push them out to SourceForge. The files (and associated md5s) are: 9fa020efb06f5485628c646451b927c6 *boost_1_55_0b1_rc1.tar.gz 02d26b038ac96f19c3478d0c45a63c9b *boost_1_55_0b1_rc1.tar.bz2 de5f7d60b2387c4fe3d03eb327f095a9 *boost_1_55_0b1_rc1.zip 7deb9063846873452e6ec6918cb75a87 *boost_1_55_0b1_rc1.7z Thanks, --The release managers

7 13

Boost result_of maintainer
by Daniel Walker 07 Oct '13

07 Oct '13

Hi all, I have been the maintainer of boost::result_of since Doug Gregor handed it over to me a few years ago, but my circumstances are changing, and I'm afraid it's time for me to hand the library over to someone else. Any volunteers? - Daniel

3 5

boost 153 interprocess_mutex much slower in windows 7 than xp?
by Noll, Jeffrey T UTAS 07 Oct '13

07 Oct '13

We have 3 processes that are synchronized with an interprocess mutex. Basically one of them has a multiplier which allows the others to run at a synchronized accelerated rate. Under XP we typically can get it to run at 5000 times realtime. New desktop refreshes are coming out running Windows 7 and the same code with faster machines with more memory are maxing out at 250 times with 95%+ cpu idle time. Am new to boost so am wondering if we're doing something wrong. Here's the crux of the code. 3 processes and some shared memory. Share memory defines struct ds_control_sync { boost::interprocess::interprocess_mutex mutex; //Mutex to protect access to the queue boost::interprocess::interprocess_condition cond_running; //Condition to wait when the control software is running boost::interprocess::interprocess_condition cond_timestep; //Condition to wait until the control software is to run again }; struct ds_plant_sync { boost::interprocess::interprocess_mutex mutex; //Mutex to protect access to the queue boost::interprocess::interprocess_condition cond_running; //Condition to wait when the plant software is running boost::interprocess::interprocess_condition cond_timestep; //Condition to wait until the plant software is to run again }; Control process has a thread that waits for a signal to run once. DWORD __stdcall Control_Sync (LPVOID) { scoped_lock<interprocess_mutex> lock(sm_control_sync->mutex); while (1) { sm_control_sync->cond_running.notify_one(); sm_control_sync->cond_timestep.wait(lock); ns_common::TimeProfile_Periodic (&sm_io->status.control_sync, &sync_first, &sync_time); Control_PWM (); if (control_run) { Control_Run (); control_run = FALSE; } else { control_run = TRUE; } ns_common::TimeProfile_Execution (&sm_io->status.control_sync, &sync_first, &sync_time); } } Plant process has the same sort of thing DWORD __stdcall Plant_Sync (LPVOID) { scoped_lock<interprocess_mutex> lock(sm_plant_sync->mutex); while (1) { sm_plant_sync->cond_running.notify_one(); sm_plant_sync->cond_timestep.wait(lock); ns_common::TimeProfile_Periodic (&sm_io->status.plant_sync, &sync_first, &sync_time); Plant_Run (); ns_common::TimeProfile_Execution (&sm_io->status.plant_sync, &sync_first, &sync_time); } } And then main process counts down a multiplier to increase it's run rate. In this case 10000X boost::interprocess::scoped_lock<boost::interprocess::interprocess_mutex> plant_lock(plant_sync.mutex); boost::interprocess::scoped_lock<boost::interprocess::interprocess_mutex> control_lock(control_sync.mutex); mult = 10000; if(mult > 1) { iterations = 0; while(mult-- > 0) { plant_sync.cond_timestep.notify_one(); control_sync.cond_timestep.notify_one(); plant_sync.cond_running.wait(plant_lock); control_sync.cond_running.wait(control_lock); iterations++; } } Works great under XP, our new Windows 7 desktops it are dog slow by a factor of around 50. Any ideas why this would be? Thanks! Jeffrey Noll Software Engineer (860)654-6378 CONFIDENTIALITY WARNING: This email may contain privileged or confidential information and is for the sole use of the inteded recipients. Unauthorized disclosure or use of this communication is prohibited. If you believe that you have received this email in error, please notify the sender immediately and delete it from your system.

5 5

Re: [boost] boost 153 interprocess_mutex much slower in windows 7 than xp?
by jim＠jc-bell.com 07 Oct '13

07 Oct '13

> We have 3 processes that are synchronized with an interprocess mutex. > Basically one of them has a multiplier which allows the others to run at a > synchronized accelerated rate. Under XP we typically can get it to run at > 5000 times realtime. New desktop refreshes are coming out running Windows > 7 and the same code with faster machines with more memory are maxing out > at 250 times with 95%+ cpu idle time. > > Am new to boost so am wondering if we're doing something wrong. Here's the > crux of the code. 3 processes and some shared memory. > ... It might be hitting the disk when it shouldn't be. Try pointing SysInternals' ProcMon at each and see if one's doing file accesses where the other isn't. (SysInternals.com.)

1 0

[interest] rich-typed smart pointers
by Julian Gonggrijp 07 Oct '13

07 Oct '13

Dear Boost members, I have designed a smart pointer that relies on the type system to offer safe and flexible automatic memory management at no runtime cost. It combines single ownership as in std::unique_ptr and reliable access from multiple places as in std::shared_ptr with some additional features. I believe it to be about as safe and practically useful as a smart pointer in C++11 could get. Further explanation and a proof-of-concept implementation is available over here: https://github.com/jgonggrijp/rich-typed-pointers There is no license yet, but you have my explicit permission to try the library and the example programs at your own risk. :-) Could this library be useful addition to Boost? I look forward to your comments. Thanks in advance, -Julian PS: a possible minor seed for discussion is the current lack of an implicit cast to bool. I agree with Jeff Flinn's argument why the implicit cast may be desirable [1]. However, it interferes with the comparison operators when one of the operands should be implicitly cast to weak_ptr, as explained in [2]. I could repeat myself and write comparison functions for all possible overloads, but this seems inelegant. [1] http://boost.2283326.n4.nabble.com/Looking-for-thoughts-on-a-new-smart-poin… [2] https://github.com/jgonggrijp/rich-typed-pointers/commit/89fcf2821cb39bbb9f…

5 24

[utility][enable_if]Fiddly function lookup failure on msvc11
by 山本賢一 07 Oct '13

07 Oct '13

Hi, I found a part of my code failed to compile with boost::enable_if_c when I was porting my code for msvc11 (Visual Studio 2012). The original code was bit too complex but I simplified it to boil down the issue. The simplified code is eventually like this: #include <boost/mpl/bool.hpp> #include <boost/mpl/not.hpp> #include <boost/utility/enable_if.hpp> template <class T> struct always_true : boost::mpl::true_ { }; template <class T> inline typename boost::enable_if_c< !boost::mpl::not_< always_true<T> // Argument of boost::mpl::not_ >::type::value // Refer the result of boost::mpl::not_ , int >::type get_one(T) { return 1; } void test() { get_one('a'); // Compile fails at this line with error C2893 } msvc11 fails to resolve the call to get_one() but I believe the code is definitely correct. With some more extra test, I found: (1)The same code compiles on msvc10 (Visual Studio 2010) and msvc9 (Visual Studio 2008). (2)If I changed the line I commented "//Argument of boost::mpl::not_" to "boost::mpl::true_", the code compiled on msvc11. template <class T> inline typename boost::enable_if_c< !boost::mpl::not_< boost::mpl::true_ // *** Argument of boost::mpl::not_ >::type::value // Refer the result of boost::mpl::not_ , int >::type get_one(T) { return 1; } (3)If changed the line I commented "// Refer the result of boost::mpl::not_" to ">::value", the code compiled on msvc11. template <class T> inline typename boost::enable_if_c< !boost::mpl::not_< always_true<T> // Argument of boost::mpl::not_ >::value // *** Refer the result of boost::mpl::not_ , int >::type get_one(T) { return 1; } The issue seems to be rather a compiler quirk of msvc11 than a enable_if's problem, but I posted the issue here because we need a workaround to avoid it (on msvc11) when we use enable_if. Please let me know if you have any idea about the issue. Thanks. Yamamoto

3 3

[algorithm] documentation mistakes in 'equal' and 'mismatch'
by Takatoshi Kondo 06 Oct '13

06 Oct '13

Hi, Marshall IIUC, I found some mistakes in the documentation of 'equal' and 'mismatch'. http://www.boost.org/doc/libs/1_54_0/libs/algorithm/doc/html/algorithm/CXX1… http://www.boost.org/doc/libs/1_54_0/libs/algorithm/doc/html/the_boost_algo… In the first code block, auto seq1 = { 0, 1, 2 }; auto seq2 = { 0, 1, 2, 3, 4 }; std::equal ( seq1.begin (), seq1.end (), seq2.begin ()); // true std::equal ( seq2.begin (), seq2.end (), seq1.begin ()); // Undefined behavior std::equal ( seq1.begin (), seq1.end (), seq1.begin (), seq2.end ()); // false The second seq1.begin() in the last line should be seq2.begin() as follows. std::equal ( seq1.begin (), seq1.end (), seq2.begin (), seq2.end ()); // false Similarly, std::mismatch ( seq1.begin (), seq1.end (), seq1.begin (), seq2.end ()); // <3, 3> should be std::mismatch ( seq1.begin (), seq1.end (), seq2.begin (), seq2.end ()); // <3, 3> Thanks, Takatoshi

2 1

[svn] Server problems?
by Rene Rivera 06 Oct '13

06 Oct '13

I'm getting a persistent error on te SVN server like so: === Froggy:trunk grafik$ svn up Updating '.': svn: E175002: Server sent unexpected return value (413 Request Entity Too Large) in response to REPORT request for '/svn/boost/!svn/vcc/default' === Any ideas? Rene -- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

2 1

[circular-buffer] Missing images.
by Daniel James 06 Oct '13

06 Oct '13

Hi, I made a change to try to fix some broken links in the circular buffer documentation: https://svn.boost.org/trac/boost/changeset/86174/ You can see the broken links in the inspect report: http://boost.cowic.de/rc/docs-inspect-trunk.html#doc Although hopefully in a couple of hours they'll be gone. But there are still a couple of links to images which I can't find: 'circular_buffer.png' and 'space_optimized.png', did someone forget to check them in? It's probably best not to check them in at 'libs/circular_buffer/doc/html/images', but instead at something like 'libs/circular_buffer/doc/images', that way the images are kept separate from generated documentation. I'll help get the image links right, as it's more tricky than it should be. thanks, Daniel

1 0

[regression] Beagle Bone Black
by Jim Bell 05 Oct '13

05 Oct '13

For anyone interested, Boost regression tests fare pretty well on the $45 Beagle Bone Black (beaglebone.org) Stop by the release regression matrix and check it out (http://www.boost.org/development/tests/release/developer/summary.html) And while you're over there, investigate & fix a regression test failure on your platform: submit a patch and make the matrix a greener place! (See http://www.boost.org/development/bugs.html.) Cheers! -Jim

1 0

[log] logger linking problem
by Tadeusz Jordan 05 Oct '13

05 Oct '13

Hi everyone, I have been using Boost for some time now and really like it. Unfortunately, recently I have bumped into a linker issue when trying to use boost::log, was wondering if anyone has seen this before, or has any insights … thank you very much. The problem is described in the below post. http://stackoverflow.com/questions/18881602/boost-logger-linking-issue -- Sincerely, Tadeusz Jordan Software Engineer at The Broad Institute of MIT and Harvard MS Candidate in CS at Northeastern University This email message and any attachments are confidential and may be privileged. It is intended only for the individual or individuals to whom it is addressed and may not be saved, copied, printed, disclosed or otherwise used by anyone else. If you are not the intended recipient, kindly notify the sender and delete this email and any attachments immediately.

3 11

Re: [boost] [type_traits][function_types] Discard param const qualification, bug or feature?
by Sergey Zhuravlev 05 Oct '13

05 Oct '13

Signature type int(int, const std::string) can be used as parameter for some compiletime algorithm. For example, algorithm that generate new signature type with optimal transfer arguments int (int, const std::string&) or generate signature with all argument references int (int&, const std::string&) Can't use type_traits, function_types at that cases, because const be omitted. This will lead to compiletime error, if function with first signature call function with second signature and use arguments from function with first signature for this call. Signature type void(int, const std::string) can use as types tuple for some compiletime algorithm. Can't use type_traits, function_types, at that case, because const be lost. Signature type void(int, const std::string) can use as parentheses dropper for "types list", e.g. for macro parameter. (int, const std::string) => int, const std::string. Can't use type_traits, function_types, at that case, because const be lost. I think default behavior is correct, but need parameter for change this behavior. At least function_types.

6 16

lots of warning with gcc-4.8.1 + boost-1.54.0
by Neal Becker 04 Oct '13

04 Oct '13

Lots of warnings like this: ./boost/bind/arg.hpp:37:22: warning: typedef ‘T_must_be_placeholder’ locally defined but not used [-Wunused-local-typedefs] when building 1.54.0 with gcc-4.8.1 (fedora f19)

8 9

[log] MSVC 9 build hangs
by Andrey Semashev 04 Oct '13

04 Oct '13

Hi, Many test results for Boost.Log on teeks99-03b-win2008-64on64 [1] show that the build aborts due to timeout. From the test setup description (2 GiB of RAM, 2 CPUs, 4 build jobs) it seems that the problem could be in the insufficient system resources. 4 jobs building Boost.Log can easily exceed 2 gigs of RAM, especially considering some of the memory is reserved by OS and other programs. If there isn't any swap, the build may be just aborting, and if there is, it's probably performing dead slow. And 2 cores might also be too limiting. Could the tester take a look what is happening on that setup? If it's not a resource problem, then I would appreciate any information on the problem. [1] http://www.boost.org/development/tests/trunk/developer/log.html

3 27

[ASIO] Safely shut down timer thread in boost::asio::io_service in Windows DLL
by Bo Peng 03 Oct '13

03 Oct '13

Hi folks, As you might already know, Windows DLL has quite some limitation about what you can do during its loading and unloading. For example, you can't 'join' a thread when unloading a DLL. The consequence of doing that, from my opinion, is quite serious: it will hang the process in a dead lock. I have a Windows DLL, which uses boost::asio::deadline_timer. I found that deadline_timer::async_wait creates a timer thread as a private member of io_service. This thread won't be shut down even if all the timers are cancelled. In the destructor of io_service, 'join' will be called on the thread. In some exceptional situation, users might exit their main function before destructs the io_service inside my DLL, so the destructor is called during the unloading of the DLL, which hangs their process. The following code demonstrates this issue. action.h and action.cpp are the code for the dll, main.cpp are the code for the application which uses the dll. action.h: #pragma once #ifndef _WIN32_WINNT #define _WIN32_WINNT 0x0501 #endif extern "C" __declspec(dllexport) void start(); extern "C" __declspec(dllexport) void stop(); action.cpp: #include "action.h" #include <boost/asio.hpp> #include <boost/bind.hpp> #include <boost/shared_ptr.hpp> #include <boost/thread.hpp> class Action { public: Action() : ios_(), timer_(ios_, boost::posix_time::seconds(1)), worker_() { } void start() { worker_.reset(new boost::thread(boost::bind(&Action::startEntry, this))); } void stop() { if (worker_) { ios_.post(boost::bind(&Action::stopEntry, this)); worker_->join(); worker_.reset(); } } private: void startEntry() { timer_.async_wait(boost::bind(&Action::timerHandler, this, _1)); ios_.run(); } void stopEntry() { timer_.cancel(); } void timerHandler(const boost::system::error_code& e) { if(e == boost::asio::error::operation_aborted) { std::cout << "Finished." << std::endl; } else { std::cout << "Triggered." << std::endl; timer_.expires_from_now(boost::posix_time::seconds(1)); timer_.async_wait(boost::bind(&Action::timerHandler, this, _1)); } } boost::asio::io_service ios_; boost::asio::deadline_timer timer_; boost::shared_ptr<boost::thread> worker_; }; boost::shared_ptr<Action> action; void start() { action.reset(new Action); action->start(); } void stop() { if (action) { action->stop(); action.reset(); } } main.cpp: #include <iostream> #include <windows.h> int main() { typedef void (__cdecl *PROC)(); HINSTANCE hInstLib = LoadLibrary(TEXT("dll.dll")); if (hInstLib == NULL) { std::cout << "Failed to load dll" << std::endl; return 1; } PROC startProc = reinterpret_cast<PROC>(GetProcAddress(hInstLib, "start")); if (startProc == NULL) { std::cout << "Failed to load start function" << std::endl; return 1; } PROC stopProc = reinterpret_cast<PROC>(GetProcAddress(hInstLib, "stop")); if (startProc == NULL) { std::cout << "Failed to load stop function" << std::endl; return 1; } startProc(); std::cout << "Press any key to exit..." << std::endl; getchar(); //stopProc(); FreeLibrary(hInstLib); return 0; } As you can see, stopProc() is commented out to simulate that the user doesn't have the chance to call the clean up function of my DLL. What I am wondering is, is it possible to shut down the thread whenever there isn't any timer outstanding. Or if I had access to the handle of this thread, I could call TerminateThread, which is allowed even during dll unloading. Regards, Bo

2 2