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

unique_future without rvalue references
by John M. Dlugosz 16 May '12

16 May '12

I'm using Clang on the Mac without the C++11 dialect enabled in this project. With BOOST_NO_RVALUE_REFERENCES defined, in Boost 1.49, how can I write a function returning an object of type unique_future<T> ? I tried changing std::move to boost::move which I expected to work. I tried fiddling with thread_move_t explicitly. I can't get anything to work. What's the magic formula?

2 4

segmentation fault using boost asio in linux.
by mozdemir 16 May '12

16 May '12

Hi, I am using Boost Asio and hitting a segmentation fault crash in ubuntu. I don't have any issue when this is run in the windows. it runs and after half an hour, it hits this crash. Below is the code that starts from beginning to the place that the segmentation fault happened. The interesting part is that I use io_strand all over the code and I don't see any thread-safety issue. In the program I use 2 threads that run the worker io_servece.run(). I also put some printf in the HandleSend() just before the crash. i can see that itr pointer is not valid even though m_pending_sends has one element in the list that is supposed to be this itr pointer. What could be wrong here? Thanks a lot, mustafa 06:49.20 [dbg] void Connection::HandleSend() itr size: 2869978912 m_pending_sends.size(): 1 void Connection::Start() { m_stopped = false; m_start_time = boost::posix_time::second_clock::local_time(); boost::system::error_code ec; boost::asio::ip::tcp::resolver resolver( m_hive->GetService() ); boost::asio::ip::tcp::resolver::query query( m_host, boost::lexical_cast< std::string >( m_port ) ); boost::asio::ip::tcp::resolver::iterator endpointIterator = resolver.resolve( query ); Connect(endpointIterator); return; } void Connection::Connect(tcp::resolver::iterator endpoint_iter) { LDBG_ << "void Connection::Connect()-1 symbol: " << m_symbol; if (endpoint_iter != boost::asio::ip::tcp::resolver::iterator()) { boost::asio::ip::tcp::endpoint endpoint = *endpoint_iter; m_socket.async_connect( endpoint, m_io_strand.wrap( boost::bind( &Connection::HandleConnect, shared_from_this(), boost::asio::placeholders::error, endpoint_iter ) ) ); } else { Stop(); } return; } void Connection::HandleConnect( const boost::system::error_code & error, boost::asio::ip::tcp::resolver::iterator endpoint_iterator ) { LDBG_ << "void Connection::HandleConnect()-1 symbol: " << m_symbol << " error: " << error << " HasError " << HasError() << " m_hive->HasStopped() " << m_hive->HasStopped(); if ( error || HasError() || m_hive->HasStopped() ) { StartError( error ); } else { if ( m_socket.is_open() ) { OnConnect( m_path ); } else { Connect(++endpoint_iterator); } } return; } void MyConnection::OnConnect( const std::string & host, uint16_t port, const std::string & path ) { Recv(); Send(); } void Connection::Send() { if (m_stopped) return; std::string str = "GET " + m_path + " HTTP/1.0\r\n\r\n"; str += "Host: " + m_host + "\r\n"; str += "Accept: */*\r\n"; str += "Connection: keep-alive \r\n\r\n"; std::vector< uint8_t > request; std::copy( str.begin(), str.end(), std::back_inserter( request ) ); m_io_strand.post( boost::bind( &Connection::DispatchSend, shared_from_this(), request ) ); // start the heartbeat timer for the next send msg. StartTimerHeartbeat(); return; } void Connection::DispatchSend( std::vector< uint8_t > buffer ) { bool should_start_send = m_pending_sends.empty(); m_pending_sends.push_back( buffer ); if ( should_start_send ) { StartSend(); } return; } void Connection::HandleSend( const boost::system::error_code & error, std::list< std::vector< uint8_t > >::iterator itr ) { if ( error || HasError() || m_hive->HasStopped() ) { StartError( error ); } else { OnSend( *itr ); if ( !m_pending_sends.empty() ) { m_pending_sends.erase( itr ); <<<<<<<<====== Segmentation Fault happens here StartSend(); } } return; } void Connection::StartSend() { if ( !m_pending_sends.empty() ) { boost::asio::async_write( m_socket, boost::asio::buffer( m_pending_sends.front() ), m_io_strand.wrap( boost::bind( &Connection::HandleSend, shared_from_this(), boost::asio::placeholders::error, m_pending_sends.begin() ) ) ); } return; } -- View this message in context: http://boost.2283326.n4.nabble.com/segmentation-fault-using-boost-asio-in-l… Sent from the Boost - Users mailing list archive at Nabble.com.

3 7

[boost] [decimal] Proposed portable implementation ofstd::decimal
by Josh Quigley 16 May '12

16 May '12

Hi all. A first draft of this library is available at https://sourceforge.net/projects/stddecimal/ Runs on MSVC10 and gcc 4.6.3. Wraps the Intel implementation only, Until we resolve the licencing issue, top-level README contains detailed instructions about where to get 3rd party code and what to do with it. I'm keen on feedback on a particular point (although all feedback is of course welcome!): The current project can parse and execute the test cases maintained by Mike Cowlishaw from http://speleotrove.com/decimal/ (referred to as the Test Cases). To be completely clear, I also have normal, interface testing test cases, I am *not* talking about those below. - Question: How useful do people feel the Test Cases to be? I originally expected 99% of these tests to pass, but it turns out that most of them require: - The operands to be parsed and stored at the precision they appear in the Test Case file - The operation to be performed at precision of the operands - The high precision result to be rounded to the precision required by the Test Cases. - The test inputs to be parsed with correct rounding in underflow situations (not required by IEEE afaik) The above requirements are based on my experience with the tests - it is possible I'm making a blunder somewhere. Since the Test Cases are really testing the 3rd party library, an argument could be made they are not essential, or even desirable. I'm inclined to think they would be very, very nice to have, as they would give users a lot of confidence - I suspect user uptake would be poor without this confidence. So... what do people think? Regards, Josh.

1 0

Why does boost::locale::generator fail for some locale codes?
by Adrián Chaves Fernández (Gallaecio) 15 May '12

15 May '12

I am using boost::locale::generator with its default backend (ICU I assume) to generate an std::locale. But for some reason, when I pass certain locale codes to the generator, it fails and the application execution is interrupted with the following output messages: terminate called after throwing an instance of 'boost::locale::conv::conversion_error' what(): Conversion failed Abortado I have tested the following values: * gl — FAILS * gl_ES — FAILS * gl_ES.utf8 — Works * en — Works * en_US — Works * en_US.utf8 — Works Installed locales should not be the issue: [user@localhost build]$ locale -a C en_US en_US.iso88591 en_US.utf8 galego galician gl_ES gl_ES@euro gl_ES.iso88591 gl_ES.iso885915@euro gl_ES.utf8 POSIX So why might this be happening?

3 2

Re: [Boost-users] Why does boost::locale::generator fail for some locale codes?
by Ashish 15 May '12

15 May '12

Sent from my Verizon Wireless Phone "Adrián Chaves Fernández (Gallaecio) " <adriyetichaves(a)gmail.com> wrote: >I am using boost::locale::generator with its default backend (ICU I assume) to >generate an std::locale. But for some reason, when I pass certain locale codes >to the generator, it fails and the application execution is interrupted with >the following output messages: > > terminate called after throwing an instance of >'boost::locale::conv::conversion_error' > what(): Conversion failed > Abortado > >I have tested the following values: > >* gl — FAILS >* gl_ES — FAILS >* gl_ES.utf8 — Works >* en — Works >* en_US — Works >* en_US.utf8 — Works > >Installed locales should not be the issue: > > [user@localhost build]$ locale -a > C > en_US > en_US.iso88591 > en_US.utf8 > galego > galician > gl_ES > gl_ES@euro > gl_ES.iso88591 > gl_ES.iso885915@euro > gl_ES.utf8 > POSIX > >So why might this be happening? >_______________________________________________ >Boost-users mailing list >Boost-users(a)lists.boost.org >http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Boost/Asio short read error
by Marcin Głogowski 15 May '12

15 May '12

Hi, I have problem with Boost/asio - sometimes server returns "short read" error. I'm using client/server from the examples. Please write me - is it a bug or just wrong implemented example because the error occurs not every time. How to protect my application against the error? Best regards, Marcin Głogowski Dom Maklerski Banku Ochrony Środowiska Spółka Akcyjna ul. Marszałkowska 78/80 / 00-517 Warszawa wpisana w Rejestrze Przedsiębiorców prowadzonym przez Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego pod numerem: KRS 0000048901 / NIP 526-10-26-828 Kapitał zakładowy w wysokości 21.551.200zł wpłacony w całości. P - Nie drukuj tej wiadomości, jeśli to nie jest konieczne.

2 1

boost::asio The semaphore timeout period has expired
by Markus Bonk 15 May '12

15 May '12

Hi, I am getting a timeout "The semaphore timeout period has expired" from async_read_some which I do not want. What is causing it - ok, it could be that I am not receiving anything and how do I configure it? Markus

2 1

communicate with GSM MODEM
by Evaggelos Tsampazis 15 May '12

15 May '12

Hi Everyone! I would like to ask if someone knows how to use in detail the serial_port() mechanism. I want to create an API application where I will send SMS messages from the pc instead of the mobile phone/gsm modem. Of course, the mobile phone will be connected to the PC from a com or tty serial port. Despite that, I would also like to receieve the inbox from the mobile device. By other words, I need a way to send AT commands to my gsm device and then after receieve the answer. How can that be made easy? Thanks Evaggelos

1 0

Using BoostTest to run unit tests multiple times without quitting test runner
by Pankaj 15 May '12

15 May '12

I want to use Boost Test to run unit tests multiple times without quitting the test runner. Here is the pseudo-code to demonstrate what I want to do: void main() { for(int i = 0; i < 10; ++i) { char *arguments[] ={ "MyApplication.exe", "--detect_memory_leak=0" }; boost::unit_test::unit_test_main( &init_function, 2, arguments); } } The first time unit_test_main is called, all the boost tests run fine but in the second iteration, boost test throws an exception. I looked at the internal code and found that framework is initialized everytime unit_test_main is called and if framework is already initialized, boost test doesn't like initializing framework again. Please let me know if there is any way to run units test multiple times without quitting test runner. -- View this message in context: http://boost.2283326.n4.nabble.com/Using-BoostTest-to-run-unit-tests-multip… Sent from the Boost - Users mailing list archive at Nabble.com.

1 0

Re: [Boost-users] [mpl] cross product and gcc specific compiler error
by Josh Quigley 14 May '12

14 May '12

Aaaaaaaaaaaaah! Thanks a lot! Regards, Josh. > > It doesn't work because you're relying on > implementation details. Use boost::mpl::at_c<XXX, 0>::type > instead of XXX::item0. > > ... SNIP... > > In Christ, > Steven Watanabe

1 0