Re: [Boost-bugs] [Boost C++ Libraries] #4023: Read handler has EOF error_code

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #4023: Read handler has EOF error_code
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2010-03-18 09:38:16

#4023: Read handler has EOF error_code
----------------------------------+-----------------------------------------
 Reporter:  olafvdspek@…          |       Owner:  chris_kohlhoff
     Type:  Bugs                  |      Status:  new           
Milestone:  Boost 1.43.0          |   Component:  asio          
  Version:  Boost 1.42.0          |    Severity:  Showstopper   
 Keywords:                        |  
----------------------------------+-----------------------------------------

Comment(by chris_kohlhoff):

 The lines

 Replying to [comment:3 anonymous]:
 > {{{
 > XCC WOL Web
 Server.exe!boost::asio::detail::win_iocp_io_service::operation::on_completion(unsigned
 long last_error=0, unsigned long bytes_transferred=0)  Line 114 + 0x1c
 bytes       C++
 > XCC WOL Web
 Server.exe!boost::asio::detail::win_iocp_io_service::do_one(bool
 block=true, boost::system::error_code & ec={...})  Line 545 + 0x16 bytes
 C++
 > }}}

 indicate that the values:

   last_error = 0
   bytes_transferred = 0

 are the ones getting returned from the OS via GetQueuedCompletionStatus.
 So there's nothing in that particular call stack to indicate that the
 closure isn't genuine.

 You'll need to check the point where the operation is being started. E.g.
 see async_receive() starting on line 1368 of win_iocp_socket_service.hpp.
 For example, is it possible that the total_buffer_size is 0?

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/4023#comment:4>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.