- Boost-users - lists.boost.org

How to implement ping using boost::asio::ip::icmp
by michael trudgian 26 Jun '09

26 Jun '09

Hoping someone can help me. I am trying to implement a basic ICMP ping using boost::asio. The boost asio library documentation concerning ICMP is pretty scant. It illustrates how to connect an icmp socket, but not how to send an echo request packet, or any other details about how the protocol can be used. If anyone has successfully used boost::asio::ip::icmp, and has some advice on how to use it to implement a simple ICMP ping, I would be greatly appreciative. _________________________________________________________________ POP access for Hotmail is here! Click here to find out more http://windowslive.ninemsn.com.au/article.aspx?id=802246

1 0

problem with boost::program_options - unregistered option in Config File
by Hasanul Ferdaus 25 Jun '09

25 Jun '09

Thanks for your reply. I am using boost::program_options to parse a config file like below --- sample.conf --- node.initiator=true tcp.port=8080 bootstrap.hints={ip{127.0.0.1},tcp(ip,{5002})} ---------------------------- Below I give the code that tries to read the config file sample.conf and tries to get all the options mentioned in file sample.conf - ------- Code ----- void main(){ std::string configFileName("sample.conf"); boost::program_options::options_description *optionsDescription; boost::program_options::variables_map *variablesMap; optionsDescription = new boost::program_options::options_description("Configuration"); variablesMap = new boost::program_options::variables_map(); optionsDescription->add_options() ("tcp.port", "TCP Port Number") ("bootstrap.hints", "Bootstrap Hints"); std::ifstream ifs(configFileName.c_str()); store(parse_config_file(ifs, *optionsDescription, true), *variablesMap); notify(*variablesMap); if (variablesMap->count("node.initiator"){ std::cout <<(*variablesMap)["node.initiator"].as<std::string>() << "\n"; } if (variablesMap->count("tcp.port")){ std::cout <<(*variablesMap)["tcp.port"].as<std::string>() << "\n"; } if (variablesMap->count("bootstrap.hints")){ std::cout <<(*variablesMap)["bootstrap.hints"].as<std::string>() << "\n"; } delete optionsDescription; delete variablesMap; return ; } ----------------- Now, the output is like below - --- output --- 8080 {ip{127.0.0.1},tcp(ip,{5002})} --------- But the value of the option node.initiator (i.e. "true") is not shown, also there is no exception. If I pass "false" in the 3rd parameter of parse_config_file() rather than "true", it throws exception, as it should do. But my question is, why "node.initiator" option is not in the variablesMap, as parse_config_file() should have parsed both registered and unregistered options. Surely if(variablesMap->count("node.initiator") does not pass. In the following link, it is mentioned that "allow_unregistered = false" is the default argument for parse_config_file() function, but I am surely passing "true" in my code. http://www.boost.org/doc/libs/1_38_0/doc/html/boost/program_options/parse_c… In another post you mentioned that SVN HEAD supports unregistered options in config file. Just now I have build the program_option library from boost svn, but there is no difference in the result. Awaiting your response. Thank you. --- On Thu, 6/25/09, Hasanul Ferdaus <sunny_register(a)yahoo.com> wrote: From: Hasanul Ferdaus <sunny_register(a)yahoo.com> Subject: problem with boost::program_options To: boost-users(a)lists.boost.org Date: Thursday, June 25, 2009, 9:41 AM Hi, I am trying to parse unregistered options using boost::program_options for config files but it does not recognize the unregistered options. the code is like to the following - -------------------------------- boost::program_options::options_description *optionsDescription; boost::program_options::variables_map *variablesMap; optionsDescription->add_options() ("ariba.bootstrap.hints", "Bootstrap Hints"); std::ifstream ifs(configFileName.c_str()); store(parse_config_file(ifs, *optionsDescription, true), *variablesMap); notify(*variablesMap); ---------------------------------- As it says, passing true to the 3rd argument of parse_config_file() should allow unregistered options to be parsed, but it does not recognize any unregistered options in config file. If anyone knows how to enable unregistered options in config file, please respond. Thanks in advance. Sunny

2 1

Re: [Boost-users] [Boost.Test] [1.38] Automated test suie registration with muti-file-test-modules
by Greg Christopher 25 Jun '09

25 Jun '09

> > > > Hi, > > We are starting to expand the number of test modules and are having > > some growing pains. > > > > Originally we were using the "single header" variant > > included/unit_test.hpp file. Now we have switched > to linking to the > dynamic version of the boost test library > and are including > auto_unit_test.hpp. > > Just unit_test.hpp is fine. Older name is deprecated. Ok- hopefully that's true for the version mentioned in the subject line. > > > We have been counting on the Test Tools to automatically register > > suites and test cases. This still worked when we just included > > unit_test.hpp (instead of included/unit_test.hpp). > > > > However with multiple test modules, init_unit_test_suite is being > > defined in each module. > > This should work as you expect. Please post simple example > illustrating your issues. Test1.cpp: ----- #include "stdafx.h" #define BOOST_TEST_MODULE foo2 #include <boost/test/execution_monitor.hpp> #include <boost/test/unit_test.hpp> class DefaultFixture { public: DefaultFixture() { } ~DefaultFixture() {}; }; BOOST_AUTO_TEST_SUITE(foo2) BOOST_FIXTURE_TEST_CASE(foo2, DefaultFixture) { BOOST_CHECK(4 == 4) } ----- Test2.cpp: ----- #include "stdafx.h" #define BOOST_TEST_MODULE foo #include <boost/test/execution_monitor.hpp> #include <boost/test/unit_test.hpp> class DefaultFixture { public: DefaultFixture() { } ~DefaultFixture() {}; }; BOOST_AUTO_TEST_SUITE(foo) BOOST_FIXTURE_TEST_CASE(foo, DefaultFixture) { BOOST_CHECK(4 == 4); } BOOST_AUTO_TEST_SUITE_END() ----- And Link with boost library.... 1>TestCase2.obj : error LNK2005: "class boost::unit_test::test_suite * 1>__cdecl init_unit_test_suite(int,char * * const)" 1>(?init_unit_test_suite@@YAPAVtest_suite@unit_test@boost@@HQAPAD@Z) 1>already defined in basic.obj Googling around, I discovered this cryptic define done in one of the files will fix it: ----- #define init_unit_test_suite init_auto_unit_test_suite ----- A strange observation as well.... Take this code: #include "stdafx.h" #define BOOST_TEST_MODULE foo #include <boost/test/execution_monitor.hpp> #include <boost/test/unit_test.hpp> class DefaultFixture { public: DefaultFixture() { } ~DefaultFixture() {}; }; BOOST_AUTO_TEST_SUITE(foo) BOOST_FIXTURE_TEST_CASE(foo, DefaultFixture) { BOOST_CHECK(4 == 4); } BOOST_AUTO_TEST_SUITE_END() And change BOOST_FIXTURE_TEST_CASE toBOOST_TEST_CASE(foo)... it won't compile: C:\basic\test2.cpp(21) : error C2882: 'foo' : illegal use of namespace identifier in expression c:\code\main\test\bora-vmsoft\svga\tests\bat\basic\basic\test2.cpp(22) : error C2448: 'boost::unit_test::make_test_case' : function-style initializer appears to be a function definition ----- Anyway, thanks for your help. The documentation right now seems to be lacking a little bit in giving clear examples of the different styles in which we are able to do test and suite registration. Greg

1 0

changing file output suffixes
by McLemon, Sean 25 Jun '09

25 Jun '09

Hi, Our toolchain generates files ending in ".doj" for objects, so I've been trying to configure my custom toolset module to use this. My original module is based on acc.jam but qcc.jam had something that looked like it would do the trick, so I lifted that and chucked into my module: import type ; type.set-generated-target-suffix OBJ : <toolset>bfin : doj ; type.set-generated-target-suffix STATIC_LIB : <toolset>bfin : dlb ; However my build of Boost now fails, with a fairly long error tracing: smclemo@edin-angus /usr/src/boost_1_39_0 $ bjam toolset=bfin WARNING: No python installation configured and autoconfiguration failed. See http://www.boost.org/libs/python/doc/building.html for configuration instructions or pass --without-python to suppress this message and silently skip all Boost.Python targets Building C++ Boost. After the build, the headers will be located at C:\cygwin\usr\src\boost_1_39_0 The libraries will be located at C:\cygwin\usr\src\boost_1_39_0\stage\lib Use 'bjam install --prefix=<path>' if you wish to install headers and libraries to a different location and remove the source tree. C:/cygwin/usr/src/boost_1_39_0/tools/build/v2/build\property.jam:613: in find-replace from module object(property-map)@1 error: Ambiguous key <target-type>OBJ <asynch-exceptions>off <conditional>@Jamfile</C:/cygwin/usr/src/boost_1_39_0>%Jamfile</C:/cygwi n/usr/src/boost_1_39_0>.handle-static-runtime <debug-symbols>on <define>BOOST_ALL_NO_LIB=1 <define>BOOST_DATE_TIME_STATIC_LINK <define>DATE_TIME_INLINE <exception-handling>on <extern-c-nothrow>off <hardcode-dll-paths>true <host-os>windows <include>. <inlining>off <install-dependencies>off <link>static <main-target-type>LIB <optimization>off <os>NT <preserve-test-targets>on <profiling>off <python-debugging>off <python>2.5 <rtti>on <runtime-debugging>on <runtime-link>shared <stdlib>native <suppress-import-lib>false <symlink-location>project-relative <tag>@Jamfile</C:/cygwin/usr/src/boost_1_39_0>%Jamfile</C:/cygwin/usr/sr c/boost_1_39_0>.tag <target-os>windows <target>object(file-target)@429 <threadapi>win32 <threading>multi <toolset-bfin:version>8.0.7.1 <toolset>bfin <user-interface>console <variant>debug <warnings-as-errors>off <warnings>on <snip> I'm guessing I'm doing something probably a bit stupid or missing something (I'm still at the fiddling around stage yet, so this is very likely). Is anyone in the position to confirm this, or do I need to send the module around? Also is it OK that I'm posting this here, or is there a more appropriate mailing list I should be using? - Sean

2 1

[ptr_container]delete_clone and shared libraries
by Robert Dailey 25 Jun '09

25 Jun '09

On Windows, I plan to create a ptr_vector in a separate DLL and propagate it to the executable for ownership (Factory-style). The executable will be responsible for the lifetime of this ptr_vector, and will eventually result in "delete" being called on each element in the ptr_vector. However, this 'delete' will be from the executable's memory manager, when the memory was originally allocated in the shared library's memory manager, causing serious issues. It would be ideal to specify a delete_clone class that ptr_vector would use (via ADL) and would force those objects in the ptr_vector to use the 'delete' call from the DLL's memory manager, and not the executable's. I don't see that this is going to be possible, or at least able to be done easily. Since the delete_clone's operator will have to be implemented in a CPP file, so it will be included into the shared library. This also implies that I'll have to import the delete_clone's interface, since this DLL will be loaded dynamically with LoadLibrary() in Windows. I just don't see this happening. Now, if ptr_vector had a function like so: ptr_vector::set_deleter() I could give it a pointer to a global function in my DLL, and the deleter becomes fully transparent to my executable. It just has to keep the ptr_vector around and let it fall out of scope and the deleter from the DLL will be used to delete each object in the ptr_vector. However, it isn't this simple and I need advice on how I can make this work. Thanks.

2 1

problem with boost::program_options
by Hasanul Ferdaus 25 Jun '09

25 Jun '09

Hi, I am trying to parse unregistered options using boost::program_options for config files but it does not recognize the unregistered options. the code is like to the following - -------------------------------- boost::program_options::options_description *optionsDescription; boost::program_options::variables_map *variablesMap; optionsDescription->add_options() ("ariba.bootstrap.hints", "Bootstrap Hints"); std::ifstream ifs(configFileName.c_str()); store(parse_config_file(ifs, *optionsDescription, true), *variablesMap); notify(*variablesMap); ---------------------------------- As it says, passing true to the 3rd argument of parse_config_file() should allow unregistered options to be parsed, but it does not recognize any unregistered options in config file. If anyone knows how to enable unregistered options in config file, please respond. Thanks in advance. Sunny

2 1

boost test compile warnings?
by Maróy Ákos 25 Jun '09

25 Jun '09

Hi, I'm having some compile warnings even when compiling very simple boost unit test code, using boost 1.39.0, gcc 4.3.2 on linux x86_64. see the source code at the end of the e-mail, but basically I get the following: g++ -pedantic -ansi -Wno-long-long -Wall -W -O2 -L/tmp/boost/lib -I/tmp/boost/include -o tests tests.cpp In file included from /tmp/boost/include/boost/test/output/compiler_log_formatter.hpp:20, from /tmp/boost/include/boost/test/impl/compiler_log_formatter.ipp:19, from /tmp/boost/include/boost/test/included/unit_test.hpp:18, from tests.cpp:1: /tmp/boost/include/boost/test/utils/basic_cstring/basic_cstring.hpp: In instantiation of ‘boost::unit_test::basic_cstring<const char>’: /tmp/boost/include/boost/test/unit_test_log_formatter.hpp:63: instantiated from here /tmp/boost/include/boost/test/utils/basic_cstring/basic_cstring.hpp:209: warning: type qualifiers ignored on function return type /tmp/boost/include/boost/test/utils/basic_cstring/basic_cstring.hpp:218: warning: type qualifiers ignored on function return type In file included from /tmp/boost/include/boost/test/included/unit_test.hpp:22, from tests.cpp:1: /tmp/boost/include/boost/test/impl/execution_monitor.ipp: In destructor ‘boost::detail::signal_handler::~signal_handler()’: /tmp/boost/include/boost/test/impl/execution_monitor.ipp:678: warning: missing initializer for member ‘sigaltstack::ss_sp’ /tmp/boost/include/boost/test/impl/execution_monitor.ipp:678: warning: missing initializer for member ‘sigaltstack::ss_flags’ /tmp/boost/include/boost/test/impl/execution_monitor.ipp:678: warning: missing initializer for member ‘sigaltstack::ss_size’ In file included from /tmp/boost/include/boost/test/included/unit_test.hpp:31, from tests.cpp:1: /tmp/boost/include/boost/test/utils/basic_cstring/basic_cstring.hpp: In constructor ‘boost::unit_test::test_case_filter::single_filter::single_filter(boost::unit_test::const_string)’: /tmp/boost/include/boost/test/utils/basic_cstring/basic_cstring.hpp:686: warning: type qualifiers ignored on function return type /tmp/boost/include/boost/test/utils/basic_cstring/basic_cstring.hpp:701: warning: type qualifiers ignored on function return type /usr/include/c++/4.3/bits/stl_algo.h: In function ‘char* boost::debug::<unnamed>::prepare_window_title(const boost::debug::dbg_startup_info&)’: /usr/include/c++/4.3/bits/stl_algo.h:190: warning: array subscript is above array bounds /tmp/boost/include/boost/test/floating_point_comparison.hpp: At global scope: /tmp/boost/include/boost/test/floating_point_comparison.hpp:224: warning: ‘boost::test_tools::<unnamed>::check_is_close’ defined but not used /tmp/boost/include/boost/test/floating_point_comparison.hpp:246: warning: ‘boost::test_tools::<unnamed>::check_is_small’ defined but not used the source code is as simple as the following: ----------- 8< -------- cut here ---------- #include <boost/test/included/unit_test.hpp> using namespace boost::unit_test; test_suite * init_unit_test_suite(int, char ** const) { return 0; } ----------- >8 -------- cut here ---------- is this normal? Akos

1 0

Re: [Boost-users] [Accumulators] Questions about the library
by dhruva 25 Jun '09

25 Jun '09

Hello, As a user of this library in production software, I will try to answer a few of the queries that I had asked or solved during my development. ----- Original Message ---- > Date: Wed, 24 Jun 2009 22:19:42 +0300 > From: Adi Shavit > Subject: [Boost-users] [Accumulators] Questions about the library > To: boost-users(a)lists.boost.org > Message-ID: > <8004284c0906241219i73b500cfrecb2d85905b8355d(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > 1. I sometimes need to clear the contents of an accumulator. What is the > best way to do this? Since a pristine or unused accumulator object is quite small (I have not done actual measurements), I just kept 2 variables of the same accumulator type in my C++ wrapper class. I just copied the unused when ever I wanted to reset the accumulator to its original state. One is used for doing all the math and other is used to restore the state. > 2. If my platform does not support HW floating point ops, and all my > sample values are, e.g. ints, is there a way to specify that the > *computation > *and *return value itself* (i.e. result_type, e.g. the mean) will be done > in ints (naturally, at the cost of precision)? I have used UDT as I needed some extra information from the results (as I was working on data from a time series). The reverse, using a POD like int must be possible. Instead of the first argument being float/double, use an int. If that does not work, you can wrap an int in a UDT, implement some of the operators like '=', '<', '/' depending on the accumulator you plan to use (I did that as I needed to send a UDT). > 3. Is there any info about numerical stability of the algorithms used? > For example, there are several > waysto > calculate the variance, not all being equal. > The same goes for algorithmic efficiency and memory requirements. No clue on this, I would like to some complexity information so that I can choose or know the computation impact. > 4. On the same note, is there anywhere that explains/describes the actual > algorithms used? The docs show the formula used to an extent. > 5. Finally, is there an implementation of a rolling (sliding window) > incremental variance computation? Check the mean using circular buffer. I had a similar request and the author was kind enough to implement and share it (Thanks Eric for the prompt guiding you did). See under "boost/accumulators/statistics/rolling*" in Boost 1.38+ "include" folder. -dhruva Cricket on your mind? Visit the ultimate cricket website. Enter http://cricket.yahoo.com

2 1

Boost spirit "%="
by Space Ship Traveller 25 Jun '09

25 Jun '09

Hi, I'm looking at (say): template <typename Iterator> struct employee_parser : qi::grammar<Iterator, employee(), ascii::space_type> { employee_parser() : employee_parser::base_type(start) { using qi::int_; using qi::lit; using qi::double_; using qi::lexeme; using ascii::char_; quoted_string %= lexeme['"' >> +(char_ - '"') >> '"']; start %= lit("employee") >> '{' >> int_ >> ',' >> quoted_string >> ',' >> quoted_string >> ',' >> double_ >> '}' ; } qi::rule<Iterator, std::string(), ascii::space_type> quoted_string; qi::rule<Iterator, employee(), ascii::space_type> start; }; From http://svn.boost.org/svn/boost/trunk/libs/spirit/doc/html/spirit/qi/tutoria… I can't find any information as to what "%=" does. I know that from previous examples int_ % "," parses a list of ints separated by commas, but there is no information as to what %= does. If I took a guess it seems to imply that: r = r % "," - is equivalent to - r %= "," Can someone point me to some documentation? Kind regards, Samuel

2 2

Creating a boost thread in a matlab mex file causes matlab to crash
by bjs109 25 Jun '09

25 Jun '09

I'm having some issues getting matlab and boost threads to work together. I'm posting here and a number of other places as I don't think this problem fits into any one domain. Specifically, whenever I try to use boost threads within a mex file, it causes matlab to crash. My test program is: #include <boost/thread/thread.hpp> #include <boost/bind.hpp> #include "mex.h" class TestClass { public: void run(); }; void TestClass::run() { for (int n = 0; n < 5; n++) { sleep(1); } } void mexFunction(int nlhs, mxArray *plhs[], int nrhs, const mxArray *prhs[]) { TestClass tc; boost::thread *pThread = new boost::thread(boost::bind(&TestClass::run, &tc)); pThread->join(); } The matlab crash output is as follows Configuration: MATLAB Version: 7.7.0.471 (R2008b) MATLAB License: 166534 Operating System: Linux 2.6.18-128.1.6.el5.centos.plusPAE #1 SMP Thu Apr 2 13:33:12 EDT 2009 i686 GNU C Library: 2.5 stable Processor ID: x86 Family 6 Model 7 Stepping 10, GenuineIntel Virtual Machine: Java 1.6.0_04 with Sun Microsystems Inc. Java HotSpot(TM) Client VM mixed mode Default Encoding: ISO-8859-1 Fault Count: 1 Register State: eax = 00d6bf00 ebx = 003cf590 ecx = 040571cc edx = 040571d0 esi = 04057124 edi = 00000000 ebp = a72ba3b8 esp = a72ba37c eip = 56e58955 flg = 00010246 Stack Trace: [0] 0x56e58955(0x04057124, 2, 2, 2) [1] libpthread.so.0:0x0038949b(0xa72bab90, 0, 0, 0) Running GDB on the application reveals that at the time of crashing, there are 13 threads. The backtrace for the created thread / parent thread is given below: Thread 13 (created thread) #0 0x56e58955 in ?? () #1 0x0031daf2 in thread_proxy (param=0x4241124) at ./boost/function/function_template.hpp:647 #2 0x0067049b in start_thread () from /lib/libpthread.so.0 #3 0x005c742e in clone () from /lib/libc.so.6 Thread 12 (parent thread) #0 0x003da410 in __kernel_vsyscall () #1 0x00674595 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0x0031b164 in boost::detail::condition_impl::do_wait (this=0x4241140, pmutex=0x4241124) at libs/thread/src/condition.cpp:371 #3 0x0031dd51 in thread (this=0x96c9c28, threadfunc=@0x42411cc) at ./boost/thread/condition.hpp:150 #4 0x00e9a7c2 in mexFunction (nlhs=0, plhs=0x42418fc, nrhs=0, prhs=0x424195c) at threadtest.cpp:25 #5 0x003e584f in mexRunMexFile () from /usr/local/matlabR2008b/bin/glnx86/../../bin/glnx86/../../bin/glnx86/libmex.so I am using: CentOS version 5.3 Boost version 1.33.1 (the one that comes with CentOS 5.3) Matlab R2008b release GCC version 4.1.2 (again, the one that comes with CentOS 5.3) The line used to compile the code: mex -g threadtest.cpp -lboost_thread Any ideas? -- View this message in context: http://www.nabble.com/Creating-a-boost-thread-in-a-matlab-mex-file-causes-m… Sent from the Boost - Users mailing list archive at Nabble.com.

2 2