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

Writing a stratum client using boost:asio
by Jan Willem Penterman 11 Feb '16

11 Feb '16

Hi, I'm trying to write a stratum client for a cryptocurrency mining application. The mining application connects to a stratum server to receive new work to mine on and submit solutions. The stratum protocol is a simple TCP based line protocol with JSON payload. Documentation here: https://mining.bitcoin.cz/help/#!/manual/stratum-protocol I've chosen to use boost::asio, as boost is already heavily used in the fork of the project I'm building the miner for. But I'm having difficulties to understand why my current implementation doesn't work. The basic flow is as follows: 1. connect to the server. this works 2. send subscribe method. this also works 3. authorize worker(s). doesn't work. 4. stratum server should start pushing new work periodically. doesn't work. 5. submit solution when found. not implemented yet. Without authorization, the server should still start pushing work. So I've skipped step 3 for now. The source code as I have it now is available here: https://github.com/Genoil/cpp-ethereum/blob/stratum/libstratum/ The output I get from this is as follows: i 12:19:14|<unknown> Connected to stratum server coinotron.com : 3344 i 12:19:15|<unknown> {"error": null, "id": 1, "result": [["mining.notify", "91d0025c5ea54509977e3475d065169e"], "080016D0", 4]} i 12:19:15|<unknown> Subscribed i 12:19:15|<unknown> { "id": null, "method": "mining.set_difficulty", "params": [32768]} i 12:19:15|<unknown> mining.set_difficulty i 12:19:15|<unknown> {"params": ["31065", "0xc09361c52e9dddd141040cc79c52eaed382e92c1dd350324c040482a4c4ac0fa","0x5a46dd85298b0beff65ccf3006c4b5d2f7fa6ca8a5885a7f2132714fe7a48602","0x0000000200000000000000000000000000000000000000000000000000000000", true], "id": null, "method": "mining.notify"} i 12:19:15|<unknown> mining.notify >From this I can conclude that the subscription call works. Then at the end of handleResponse, I simply queue up a new async_read_until to wait for the next line of JSON to come in from the server. This also kind of works, but the idea is that after a few seconds, new work should come in as a "mining.notify". This never happens. Can anybody explain what I'm doing wrong? Regarding the mining.authorize call on line 113. I've understood from the documentation that I can send that whenever I want, so I tried to do this immediately after the subscribe method returned. But if I do this, it a) doesn't return and b) all lines after "Subscribed" don't come in any longer. This is the second problem I'm trying to figure out. I'm using this as reference, but my Python is even worse than my C++ https://github.com/slush0/stratum-mining-proxy But when I run the binaries connecting to the same host (coinotron.com:3344), I do get new work coming in... Thanks for having a look at this.

1 0

[ASIO] Newbie question - Bidirectional communication example
by Davies, John 11 Feb '16

11 Feb '16

For a simple explanation I have two processes that run on the same computer. Process 1 sends messages to Process 2 by putting the messages into an Interprocess message queue that Process 2 created. Process 2 sends messages to Process 1 by putting the messages into an Interprocess message queue that Process 1 created. The messages can be sent at any time and are not in response to each other. Very symmetrical. Now I want to put Process 1 and Process 2 on separate computers. My intent is to transfer the messages over TCP to the opposite computer without changing Process 1 or 2. So I thought I'd create two connector programs. Connector 1 creates a message queue that pretends to be the Process 2 message queue. When it gets a message, it send it over TCP the Connector 2. Connector 2 gets the message and puts it into the real Process 2 message queue. And the reverse if Process 2 has an outgoing message. I just can't find a good example to steal from. Everything I can find are more like Process 1 makes a request and Process 2 responds. So I think I have a fundamental misunderstanding of how ASIO works. ________________________________ The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.

2 1

[Test] Funny Business with vector::at() out-of-range
by Merrill Cornish 11 Feb '16

11 Feb '16

I posted a question a couple of days ago: "Throws 'Escaping' both BOOST_CHECK_THROW and try{}". I found that BOOST_CHECK_EXCEPTION which is working for me elsewhere fails the same way. So, an out-of-range std::vector::at() seems to be the common element. In the definition of at(), the out-of-range response is handled by __throw_out_of_range_fmt(). When I looked up that one, I found void __throw_out_of_range_fmt(const char*, ...) __attribute__((__noreturn__)) __attribute__((__format__(__gnu_printf__, 1, 2))); in functexcept.h. To my admittedly less-than-expert eye, there doesn't seem to be an actual throw() here. On the other hand, the entire file are entries like this for various exceptions. There are a lot of Google hits for __throw_out_of_range_fmt, but they are for unresolved references in links, apparently caused by mixed version of libraries and object. Everything I've got is compiled linked for MinGW 64-bit, GCC 5.3.0, 64-bit --std=C++14, BOOST 1_60_1 64-bit so I get none of those errors. The problem I'm seeing with my test code is that wrapping a try{} around BOOST_CHECK_THROW shows that [1] the body of the try doesn't complete; but at the same time [2] not even a catch(...) can catch the presumed throw--as if a throw isn't actually being done. So, where did the throw go? Merrill Cornish

2 1

[TEST] Throws "Escaping" both BOOST_CHECK_THROW and try{}
by Merrill Cornish 11 Feb '16

11 Feb '16

I'm running Windows 10, 64-bit; MinGW 64-bit; GCC 5.3 64-bit; and BOOST 1_60_1 Here is the relevant test code: [319] BOOST_CHECK_THROW(throw std::out_of_range("BOOST_CK_THROW test"), std::out_of_range); [320] try { [321] std::cerr << "arcsSize()" << std::endl; [322] empty1.arcsSize(Operand::DEFAULT_ARC_SET+1); [323] std::cerr << "arcsSize() did not throw" << std::endl; [324] }//try [325] catch (const std::out_of_range& ex) [326] { std::cerr << "out_of_range caught=|" << ex.what() << "|" << std::endl; } [327] catch (...) { std::cerr << "something else caught" << std::endl; } [328] [329] BOOST_CHECK_THROW(empty1.arcsSize(Operand::DEFAULT_ARC_SET+1), std::out_of_range); The original code was just the last line, line [329]. [319]-[327] was added in an attempt to characterize the problem. The error [329] got by itself was: terminate called after throwing an instance of 'std::out_of_range' what(): vector::_M_range_check: __n (which is 1) >= this->size() (which is 1) This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. SIGABRT intercepted; converted to exit(EXIT_FAILURE). arcSize() is implemented with std::vector::at() and the index is out-of-range, so it's supposed to throw std::out_of_range. That's what was detected, so why did it terminate the program? (The last line comes from my SIGABRT handler. Without it, the test executable ends up locked and can't be deleted.) Adding in all of the test lines shown above gives; [319] Operand_Test.cpp(319): info: check 'exception "std::out_of_range" raised as expected' has passed [321] arcsSize() terminate called after throwing an instance of 'std::out_of_range' what(): vector::_M_range_check: __n (which is 1) >= this->size() (which is 1) This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. SIGABRT intercepted; converted to exit(EXIT_FAILURE). Notice the explicit throw in line [319] is detected and handled properly. However, the arcSize() call from inside the try block throws, but is not caught by even catch(...) {}. Can anyone help me see what's going on here? Merrill Cornish

2 6

[Container] Regarding Trac #11957, static_vector::max_size() is higher than the capacity
by Gagan Kumar 10 Feb '16

10 Feb '16

I tried a simple fix for https://svn.boost.org/trac/boost/ticket/11957 here https://github.com/boostorg/container/pull/37/files . Can someone please review it. Regards,Gagan Kumar

1 0

Boost Variant Type Interfaces
by Ali Nakipoglu 09 Feb '16

09 Feb '16

Hi, In our project we are using boost, boost.variant very extensively. We was using methods provided by the library to interface with Variant types. Mainly : get<T>( variant ) for accessing stored values and variant.which() == Index for checking currently stored type. Overtime we realized we can improve this as : variant.getT() for accessing stored values much more nicer to write and variant.isT() or variant.which() == WHICH_T for checking currently stored type which does not depend on order of template paramters in the Variant definition. Also in some cases we wanted to be able to add type specific methods for example in our case we are using subscript operator to access recursively stored Variants variant[ "a" ].isT() or variant[ 0 ].asT() We generalized this solution for our project and published at https://github.com/FictionIO/WrappedVariant I would like to hear your comments. Do you think its a correct approach or useful? Any suggestions are welcome! Kind Regards, Ali

1 0

[Multiprecision] Runtime assertion failure with clang++3.6.0 but not g++4.9.2
by mbw_bst＠mailbox.org 09 Feb '16

09 Feb '16

Dear all, this is my first post on this mailing list, so hopefully this will all be by the book. Executing the following minimal working example, which is supposed to calculate "3! == 6" via (1) a template function (2) a class template and save the result in a boost::multiprecision::mpz_int, results in unexpected behavior for clang++3.6.0, with the version of my boost library being 1.59.0. The program displays the correct result using g++4.9.2 however: #include <iostream> #include <boost/multiprecision/gmp.hpp> namespace bm = boost::multiprecision; template <std::size_t N> bm::mpz_int factorial() { return N * factorial<N-1>(); } template<> bm::mpz_int factorial<0>() { return 1; } template <std::size_t N> struct factorial2 { static const bm::mpz_int value; }; template<std::size_t N> const bm::mpz_int factorial2<N>::value = N * factorial2<N-1>::value; template<> struct factorial2<0> { static const bm::mpz_int value; }; const bm::mpz_int factorial2<0>::value = 1; int main () { std::cout << factorial<3>() << '\n'; std::cout << factorial2<3>::value << '\n'; return 0; } The output for clang, having been compiled via clang++ -std=c++14 -stdlib=libc++ -DNDEBUG -o main main.cpp -lgmp will result in: 6 0 However, omitting the NDEBUG flag will trigger an assertion failure: main: /usr/include/boost/multiprecision/gmp.hpp:1296: const mpz_t &boost::multiprecision::backends::gmp_int::data() const: Assertion `m_data[0]._mp_d' failed. Aborted (core dumped) Compiling the same program with g++4.9.2 (with or without "-DNDEBUG") yields the expected result: 6 6 What did I miss? Can this behavior indeed be traced down to Boost.Multiprecision, or does it have to do with the initialization order of static const class members? Or something else? Additionally, both variants work correctly with clang when using a built-in type like 'int'. Any help in understanding the problem on hand would be greatly appreciated! Best Regards, mbw

3 5

Re: [Boost-users] [Multiprecision] Runtime assertion failure with clang++3.6.0 but not g++4.9.2
by mbw_bst＠mailbox.org 09 Feb '16

09 Feb '16

Hello again and thanks for your replies! Taking the following two statements into account: > For type int, the values are computed recursively at compile time, for a > user-defined-type the values are computed at runtime and you hit > initialization-order issues. > Seems to be that Multiprecision relies on static data that haven't > (necessarily) been initialized before your own static members. Works > fine > if the members are made non-static: Does that mean that, since a) boost::multiprecision::number<gmp_int> is not constexpr enabled, and b) static initialization can't happen at compile-time for user-defined types, that there is no way for me to initialize a variable of this type at compile-time? Does b) follow logically from a) ? I (believe to have) confirmed runtime-initialization by running valgrind, which showed the presence of dynamic memory allocations (and also jumps depending on uninitialized variables, which probably corresponds to the assertion failure). I am mentioning this because initially my little test program looked somewhat like this: #include <iostream> #include <vector> #include <boost/multiprecision/gmp.hpp> namespace bm = boost::multiprecision; template<std::size_t N> struct factorial { static const bm::mpz_int value; static void add_values(std::vector<bm::mpz_int>& vec) { factorial<N-1>::add_values(vec); vec.push_back(value); } }; template<std::size_t N> const bm::mpz_int factorial<N>::value = N * factorial<N-1>::value; template<> struct factorial<std::size_t{0}> { static const bm::mpz_int value; static void add_values(std::vector<bm::mpz_int>& vec) { vec.push_back(value); } }; const bm::mpz_int factorial<0>::value = 1; int main () { std::vector<bm::mpz_int> fac_table{}; factorial<10'000>::add_values(fac_table); std::cout << "Enter a number between 0 and 10'000 to calculate factorial:"; std::size_t number; std::cin >> number; std::cout << '\n' << number << "! == " << fac_table[number] << '\n'; return 0; } This still includes the "unsafe" static initialization of a user-defined type. However it compiles and runs via g++ -ansi -std=c++14 -O3 -Wall -Wextra -pedantic -static -save-temps -ftemplate-depth-50000 -DNDEBUG -o main main.cpp -lgmp -pthread This was what made me believe in the compile-time computation of the factorials in the first place, since using this version, valgrind does not show any dynamic memory allocation at all. On the other hand, I don't understand what's going on here really, especially since std::vector<> is supposed to allocate memory at run-time. Now I'm not sure whether the last example has anything to do with Boost.Multiprecision anymore, so while it would really make my day if you could help me better understand this, I will understand if this is not the right place to ask these questions. Thanks again for your replies so far, they have been of great help! Cheers, Max

2 1

[gsoc16] ATTN: Project ideas deadline 19th Feb
by Niall Douglas 07 Feb '16

07 Feb '16

Tomorrow 8th February the application period for Google Summer of Code 2016 begins, and yet we have just *one* idea on the ideas page: https://svn.boost.org/trac/boost/wiki/SoC2016 We need *plenty* more if we are to be approved again this year as a Google Summer of Code org, the deadline for which is the 19th February. So if you have some project ideas and think you could mentor a student this summer, *please* consider adding a project idea to the ideas list or stepping forward with a list of Boost libraries or topics you'd be willing to mentor. Our thanks in advance. --- Boost C++ Libraries Google Summer of Code 2016 admin https://svn.boost.org/trac/boost/wiki/SoC2016

1 0

download from sourceforge?
by Dan Bloomquist 07 Feb '16

07 Feb '16

I followed the link form boost.org and then through sourceforge. But sourceforge directed me to: <http://downloadbud.com/?adprovider=sourceforge_fwint&source=fw36_300x250-do…> The link is an executable! I've never heard of 'downloadbud'. Not a big deal for now, I'm running with 1.58. But I'd like to get the latest of spirit x3 before I ask questions on the spirit list that may not need asking. Is there another source for boost? Or, is this executable actually a safe extractor? Sourceforge handing over an exe when it should be be a package seems just wrong... Thanks, Dan.

2 5