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

Server failing when BOOST_ASIO_ENABLE_HANDLER_TRACKING is active
by Gonzalo Garramuno 22 Jan '14

22 Jan '14

Trying to track down when the socket closes on my program, I turned on asio debugging. Server fails when BOOST_ASIO_ENABLE_HANDLER_TRACKING is active. Its stack trace is: g Scanning dependencies of target mrViewer [ 9%] Building CXX object mrViewer/src/CMakeFiles/mrViewer.dir/core/mrvServer.o Linking CXX executable ../../../bin/mrViewer [100%] Built target mrViewer # gga@gga-laptop1 /media/Linux/code/applications/mrViewer # mar ene 01 10:04 [8] $ mrViewer /media/Linux/movies/Tangled.mov [opengl] Using hardware shader profile: NVidia NV30 [opengl] mrViewer supports YUV images through shaders. [psql] Connected to database 'assets2d_development'. The code: boost::asio::io_service io_service; tcp::endpoint listen_endpoint(tcp::v4(), s->port); server rp(io_service, listen_endpoint, s->ui); io_service.run(); fails with: @asio|1357088683.200673|0|socket@0x7f303d8d2d00.close Got signal 11, faulty address is 0x1, from 0x4d222a [bt] Execution path: [bt] mrViewer(_ZN5boost4asio6detail15task_io_service16shutdown_serviceEv+0x3a) [0x4d222a] [bt] mrViewer(_ZN5boost4asio6detail15task_io_service16shutdown_serviceEv+0x3a) [0x4d222a] [bt] mrViewer() [0x4dd2c9] [bt] mrViewer(_ZN3mrv13server_threadEPKNS_10ServerDataE+0x408) [0x4e0e58] [bt] /usr/lib/libboost_thread.so.1.48.0(+0xdda9) [0x7f304e191da9] [bt] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a) [0x7f304f7f0e9a] [bt] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f304da1ccbd] without the #define the code works reliably except sometimes the socket closes unexpectedly.

4 5

Boost.Mock ?
by Mathieu Champlon 20 Jan '14

20 Jan '14

Hello, I initially sent the following message to the boost-dev mailing list, but I'm thinking this might reach more potential users here on boost-users. Would a library for mock objects be of interest ? The documentation can be found here : http://mat007.users.sourceforge.net/boost_mock/ An archive is also available for download there : http://sourceforge.net/projects/mat007.u/files/boost-mock.zip It's been converted from turtle (http://turtle.sourceforge.net/) which was mentioned on the mailing-lists a couple of times in the past. There is a catch in that it needs Boost.Test from the release branch and doesn't compile with the trunk. The changes are minimal though and I can provide a patch if anyone is interested. Is anyone already using the library who would like to see it in Boost ? Or is anyone using another mock object library who wants to give it a go ? Or even better has anyone tried it and decided to user another library who would like to comment on it ? I would be highly interested in any feedback ! Thank you, MAT.

6 9

Question for Boost.Threads and Boost.Test
by young 20 Jan '14

20 Jan '14

According to Boost document, Boost.Test can only be statically linked. Boost.Threads can only be dynamically linked. Then what boost_unit_test_framework-vc100-mt-1_53.lib for? Is it for dynamically linked dll? what libboost_thread-vc100-mt-1_53.lib for? Is it for static library? -- View this message in context: http://boost.2283326.n4.nabble.com/Question-for-Boost-Threads-and-Boost-Tes… Sent from the Boost - Users mailing list archive at Nabble.com.

4 6

[Test] Where to learn about boost::itest::mock_object?
by Mateusz Loskot 20 Jan '14

20 Jan '14

Hi, I'm looking for a simple mocking library to use together with Boost.Test. There is Turtle (aka Boost.Mock) and googlemock. During retrospection of the big thread on Boost.Test future [1], I found this curious post by Gennadiy [2] about mock_object. I had no idea such facility lives in Boost.Test and it looks it's been there for very long time. I can't find any documentation about mock_oboject, only a couple of examples. So, I have a few questions: Is the mock_object an internal feature or is it dedicated (and ready) to use by Boost.Test users? What are basic features of this mocking facility? How does it compare to Turtle or googlemock? [1] http://thread.gmane.org/gmane.comp.lib.boost.devel/234297 [2] http://thread.gmane.org/gmane.comp.lib.boost.devel/234297/focus=234621 [3] find /home/mloskot/dev/boost/_svn/trunk/libs/test -type f | xargs grep mock_object Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

4 4

Fast IPC between Linux and Windows on the same host
by U.Mutlu 13 Jan '14

13 Jan '14

Hi, what is the fastest cross-platform IPC mechanism between Linux and Windows on the same physical host? Additional info: Host OS is Linux (Debian), Windows XP is hosted in VirtualBox. Of course TCP/IP sockets is a possibility, but I need something much faster. My preference would be to use shared memory, but is it possible in such an heterogene environment? And: can Boost.Interprocess be used for this scenario? Thx -- U.Mutlu DACOS Notdienstanlagen GmbH, Germany

4 6

Does Boost.Test cover 'golden file approach'?
by Journeyer J. Joh 13 Jan '14

13 Jan '14

Hello, I know almost nothing about 'golden file approach'. http://weblogs.java.net/blog/alexeyp/archive/2007/02/testing_command.html >From this blog, you can find the term 'golden file approach'. I want to know if Boost.Test cover this kind of testing. Can I implement 'golden file approach' with Boost.Test? If so please provide me more information about it. Thank you very much. ---------------------------------------- Journeyer J. Joh o o s a p r o g r a m m e r a t g m a i l d o t c o m ----------------------------------------

3 5

lockfree::queue restrictions and performance on linux
by Leon Mlakar 13 Jan '14

13 Jan '14

Hello, after quite a while I'm back to using Boost (and back to the list) and quite happy to see that it made significant progress since I last last used it. One of the libraries that got my attentions is lockfree, the lockfree::queue in particular, since it almost completely meets my needs. Except that I've been wondering why is it that it places the requirement for the trivial destructor on the items it stores? I mean, that really reduces its usability. Is this something inherent to its design? I guess that this has been discussed during the review but a quick digging through the archives didn't come up anything on this. The reason for asking is that I have forced the queue to accept std::shared_ptr and this seems to work almost fine, except that there seem to be an extra reference left to the item last popped, but that's something I can live with. Another thing was its performance - I ran a sort of quick benchmark (queue of shared_ptr's to item containing atomic<int> as a counter, items were popped from the queue and immediately pushed back after decrementing the counter) and its perfromance was next to stellar on OSX (with multiple consumers and producers something like forty times faster than std::queue with mutex) but very poor on Linux. While I can understand that locking runs fast on Linux due to its spinlock/futex implementation of mutexes, I have no explanation for the poor performance of lockless::queue (with two producer/consumer threads std::queue with mutex was about 15 times faster and about 20 times slower than when run on OSX on the similar hardware). Did anybody else observe the same poor performance behavior? I used Boost 1.54 and tested with both gcc 4.8 and clang 3.5 and got similar results with both. Regards, Leon

2 3

[Boost::any] Memory management using dynamic libraries
by Eugenio Bargiacchi 13 Jan '14

13 Jan '14

I'm building a framework which needs to allow communication between shared libraries which are loaded at runtime. Each shared library provides its own implementation of an abstract interface contained in the framework (called Module), and all Modules are called sequentially multiple times doing the work they need to do. Since modules need to communicate with each other with custom data types, I though of using an std::unordered_map<std::string,boost::any> kept by the framework and shared with the Modules. The map is filled and read by the modules when their code is called through the Module interface which the framework knows (virtual functions). However after a bug I realized that each boost::any value is allocated by the modules, which is logical, since the framework itself has no knowledge of the types that will be stored in the map, and thus the code to allocate them must reside in the libraries themselves. I was wondering whether this could be a problem both during overwriting of a map value (since boost::any has to destroy its old contents) and during program shutdown. This could maybe be because modules use their own allocators. The problem that I had, for example, resulted in a segfault if I tried to unload the modules from memory before the destruction of the map (which is owned by the framework), during boost::any destruction. I assume this happened because the contents of boost::any were created in memory that was then unloaded during the unloading of the shared libraries, resulting in the segfault. And this yet does not take into account custom allocators! So I'm wondering what the best approach here would be. If I would need to keep track of the current "owner" of each single boost::any value allocated, and use it to manually destroy instances when required, or if there is a better way, maybe using some particular boost::any property. Many thanks in advance!

3 3

[Test] using output_test_stream to compare in the middle of a file
by Lloyd 13 Jan '14

13 Jan '14

Hi, We need to test a function which reads a "record" from a binary file. We want to compare the buffer with the "record" in input file.We know the offset of the record in input file. How can we compare the output_test_stream with a certain offset (and length) of the file? or is there any alternative for this? Thanks, Lloyd

2 1

Boost.Test segfault clang++3.3 macports cmake
by Dave Gomboc 13 Jan '14

13 Jan '14

I am getting a segmentation fault when attempting to use Boost.Test. I suspect that I don't have something set up correctly -- your assistance in remedying this would be appreciated. I am using clang++-mp-3.3 as installed by MacPorts on OS X 10.8.4. Here's the crash, which occurs after Boost.Test reports "*** No errors detected". Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: 13 at address: 0x0000000000000000 0x000000010006f6d6 in boost::unit_test::test_unit::~test_unit () (gdb) bt #0 0x000000010006f6d6 in boost::unit_test::test_unit::~test_unit () #1 0x000000010003bb5f in boost::unit_test::master_test_suite_t::~master_test_suite_t () #2 0x000000010003bcdd in boost::unit_test::framework_impl::~framework_impl () #3 0x00007fff8f465307 in __cxa_finalize () #4 0x00007fff8f466f57 in exit () #5 0x00007fff96ddc7e8 in start () (gdb) Here's a somewhat simplified version of what I have: ==== UseBoostUnitTestFramework.hpp ==== #pragma clang diagnostic push #pragma clang diagnostic ignored "-Wall" #pragma clang diagnostic ignored "-Wdisabled-macro-expansion" #pragma clang diagnostic ignored "-Wexit-time-destructors" #pragma clang diagnostic ignored "-Wextra-semi" #pragma clang diagnostic ignored "-Wglobal-constructors" #pragma clang diagnostic ignored "-Wmissing-prototypes" #pragma clang diagnostic ignored "-Wsign-conversion" #pragma clang diagnostic ignored "-Wundef" #pragma clang diagnostic ignored "-Wweak-vtables" #include <boost/test/unit_test.hpp> #pragma clang diagnostic pop ==== HaveBoostUnitTestFrameworkDefineMain.cpp ==== #define BOOST_TEST_MODULE All_Tests #include "UseBoostUnitTestFramework.hpp" /* commenting out the next 3 lines makes no difference */ namespace boost { namespace unit_test { namespace framework { master_test_suite_t & master_test_suite(); } } } // namespace boost::unit_test::framework ==== CMakeLists.txt ==== cmake_minimum_required(VERSION 2.8.10 FATAL_ERROR) cmake_policy(VERSION 2.8.10) project (Foo) add_definitions(-DBOOST_TEST_DYN_LINK) add_library (foo SHARED Foo1.hpp more files... UseBoostUnitTestFramework.hpp Foo1.cpp more files... ) find_package(Boost COMPONENTS unit_test_framework REQUIRED) include_directories(${Boost_INCLUDE_DIRS}) file(GLOB_RECURSE test_source_files *.unit_tests.cpp) link_directories(${Boost_LIBRARY_DIRS}) add_executable(all_tests HaveBoostUnitTestFrameworkDefineMain.cpp ${test_source_files}) target_link_libraries(all_tests foo ${Boost_UNIT_TEST_FRAMEWORK_LIBRARY} ) set(CTEST_OUTPUT_ON_FAILURE TRUE) enable_testing() add_test(all_tests all_tests) set(CMAKE_C_COMPILER "clang-mp-3.3") set(CMAKE_C_FLAGS "-Weverything --std=c11 -O3 -DNDEBUG") set(CMAKE_CXX_COMPILER "clang++-mp-3.3") set(CMAKE_CXX_FLAGS "-ferror-limit=1 --std=c++1y -stdlib=libc++ -Weverything -Wno-c++98-compat -Wno-c++98-compat-pedantic -Wno-padded -O3 -DNDEBUG") ==== Foo1.hpp ==== (has declarations, but nothing that depends on Boost at all -- nor does any other non-test file) ==== Foo1.cpp ==== (has definitions, but nothing that depends on Boost at all -- nor does any other non-test file) ====Foo1.unit_tests.cpp ==== #include "Foo1.hpp" #include <string> #pragma clang diagnostic push #pragma clang diagnostic ignored "-Wglobal-constructors" #include "UseBoostUnitTestFramework.hpp" BOOST_AUTO_TEST_SUITE(Bar1) BOOST_AUTO_TEST_CASE(foobar1) { BOOST_CHECK_EQUAL(std:string("a"), std::string("a")); } BOOST_AUTO_TEST_CASE(foobar2) { BOOST_CHECK_EQUAL(true, true); } BOOST_AUTO_TEST_SUITE_END() BOOST_AUTO_TEST_SUITE(Bar2) BOOST_AUTO_TEST_CASE(barfoo1) { BOOST_CHECK_EQUAL(1, 1); } BOOST_AUTO_TEST_CASE(barfoo2) { BOOST_CHECK_EQUAL(0, 0); } BOOST_AUTO_TEST_SUITE_END() #pragma clang diagnostic pop

3 2