c++ - Boost Socket 在 close() 上崩溃

Question

我们有一个与服务器对话的 C++ 应用程序。它向它发送两条消息，服务器用另一条消息响应每条消息。我们使用的是 Boost，但是当我们试图关闭套接字时，Boost 套接字——整个应用程序——都会失败。

这是我们正在做的事情的总体思路:

1. 对消息进行编码(将其更改为字符串)
2. 打开套接字
3. 发送消息
4. 检查发送的字节数
5. 查看返回信息
6. 关闭并关闭套接字

因为我们发送了两条消息，所以我们在一个循环中执行(显然只有两次迭代)。

我们确切地知道错误在哪里，因为如果我们删除该行，它就可以正常工作。它在第 5 步。不幸的是，这是一个重要的步骤。我们找不到我们做错了什么如何解决它。

代码如下:

bool ReallyImportantService::sendMessages( int messageNum ) {

    // ...some error-checking here...

    bool successCode = false;
    for( int i = 0; i < 2; ++i ) {

        successCode = false;

        unique_ptr<boost::asio::ip::tcp::socket> theSocket = connect();

        if( theSocket == nullptr ) {
            theLogger->error( "Could not create socket, could not send input messageNum to service" );
            return successCode;
        }

        string message = encodeMessage( messageNum );

        // send the message
        boost::system::error_code error;
        size_t bytesSent = boost::asio::write(*theSocket,
                                       boost::asio::buffer(message),
                                       boost::asio::transfer_all(), error);

        // inspect the result
        if( !messageNumSendSuccessful(message.length(), bytesSent) ) {
            return successCode;
        }

        // Get the response message
        string response;
        boost::system::error_code e;
        boost::asio::streambuf buffer;

        // this is step #5 above, the line that kills it. But it responds with no errors
        boost::asio::read_until(*theSocket, buffer, "\0", e);

        if( e.value() == boost::system::errc::success ) {
            istream str(&buffer);
            getline(str, response);

            // validate response
            successCode = messageAckIsValid( response, messageNum );
        }
        else {
            theLogger->error( "Got erroneous response from server when sending messageNum" );
        }

        // close it all up
        boost::system::error_code eShut;
        theSocket->shutdown(boost::asio::socket_base::shutdown_type::shutdown_both, eShut);
        // We never get an error code here, all clean

        try {
            boost::system::error_code ec;

            // This is where it all goes belly-up. It doesn't throw an exception, doesn't return an 
            // error-code. Stepping through, we can see the call stack shows a Segmentation fault, 
            // but we don't know what could be causing this.
            theSocket->close( ec );
        }
        catch(boost::system::system_error& se) {
            theLogger->error( "sendMessages() barfed on close! " + string(se.what()) );
        }
        catch( ... ) {
            theLogger->error( "sendMessages() barfed on close! " );
        }
    }
    return successCode;
}

string ReallyImportantService::encodeMessage( int messageNum ) {

    // Encode the message
    stringstream ss;
    ss << "^FINE=";
    ss << to_string(messageNum) << "\n";
    string message = ss.str();

    theLogger->info( message );

    return message;
}

unique_ptr<boost::asio::ip::tcp::socket> ReallyImportantService::connect() {
    // Addresses from configuration
    string address( server_ip );
    string port( server_port );

    // Resolve the IP address
    boost::asio::io_service ioService;
    boost::asio::ip::tcp::resolver resolver(ioService);
    boost::asio::ip::tcp::resolver::query query(address, port);
    boost::asio::ip::tcp::resolver::iterator ep_iterator = resolver.resolve(query);

    // create the socket
    unique_ptr<boost::asio::ip::tcp::socket> theSocket = make_unique<boost::asio::ip::tcp::socket>(ioService);

    // not sure if this is necessary, but couldn't hurt; we do reuse the IP address the second time around
    boost::system::error_code ec;
    theSocket->set_option(boost::asio::socket_base::reuse_address(true), ec);

    // Connect
    try {

        boost::asio::connect(*theSocket, ep_iterator);

    } catch(const boost::system::system_error &e){
        theSocket = nullptr;
        theLogger->error( "Exception while attempting to create socket: " + string(e.what()) );
    } catch(const exception &e){
        theSocket = nullptr;
        theLogger->error( "Exception while attempting to create socket: " + string(e.what()) );
    }

    return theSocket;
}

这是出错时我们得到的调用堆栈:

(Suspended : Signal : SIGSEGV:Segmentation fault)   
    pthread_mutex_lock() at 0x7ffff7bc8c30  
    boost::asio::detail::posix_mutex::lock() at posix_mutex.hpp:52 0x969072 
    boost::asio::detail::scoped_lock<boost::asio::detail::posix_mutex>::scoped_lock() at scoped_lock.hpp:36 0x980b66    
    boost::asio::detail::epoll_reactor::free_descriptor_state() at epoll_reactor.ipp:517 0x96c6fa   
    boost::asio::detail::epoll_reactor::deregister_descriptor() at epoll_reactor.ipp:338 0x96bccc   
    boost::asio::detail::reactive_socket_service_base::close() at reactive_socket_service_base.ipp:103 0xb920aa 
    boost::asio::stream_socket_service<boost::asio::ip::tcp>::close() at stream_socket_service.hpp:151 0xb975e0 
    boost::asio::basic_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> >::close() at basic_socket.hpp:339 0xb94f0d    
    ReallyImportantService::sendMessages() at ReallyImportantService.cc:116 0xb8ce19    
    <...more frames...> 

我们创建了一个最小的实现，它只是:

1. 创建套接字
2. 关闭套接字
3. 关闭套接字

而且效果很好。我们把它放在一个循环中，我们可以毫无问题地进行几十次迭代。

我们使用 Eclipse CDT 和 gcc 进行编译。

知道会发生什么吗？

Answer 1

你违反了基本规则。

io_service 必须比在其上创建的所有对象都长。

您的 connect() 函数创建一个 io_service，在其上创建一个套接字并返回套接字(包装在一个 unique_ptr 中)。然后io_service被销毁。

从那时起，所有赌注都被取消了，因为套接字将使用与您刚刚销毁的 io_service 关联的套接字服务对象。该套接字服务现在只是其中包含未定义值的内存。你是(不)幸运的程序在段错误之前已经走了这么远。

一般来说，每个应用程序都需要一个io_service。所有需要它的对象都应该带有对它的引用。

然后您的连接函数变为:

bool connect(boost::asio::ip::tcp& theSocket) {
    // Addresses from configuration
    string address( server_ip );
    string port( server_port );

    // Resolve the IP address
    boost::asio::ip::tcp::resolver resolver(theSocket.get_io_service());
    boost::asio::ip::tcp::resolver::query query(address, port);
    boost::asio::ip::tcp::resolver::iterator ep_iterator = resolver.resolve(query);

    // not sure if this is necessary, but couldn't hurt; we do reuse the IP address the second time around
    boost::system::error_code ec;
    theSocket.set_option(boost::asio::socket_base::reuse_address(true), ec);

    // Connect
    try {

        boost::asio::connect(theSocket, ep_iterator);

    } catch(const boost::system::system_error &e){
        theSocket = nullptr;
        theLogger->error( "Exception while attempting to create socket: " + string(e.what()) );
        return false;
    } catch(const exception &e){
        theSocket = nullptr;
        theLogger->error( "Exception while attempting to create socket: " + string(e.what()) );
        return false;
    }

    return true;
}

bool sendMessages(boost::asio::io_service& ios, int messageNum)
{
    boost::asio::ip::tcp::socket theSocket(ios);
    auto ok = connect(theSocket);

    // ... carry on ...

}

• 尽可能保留对套接字等的引用。将它们包装在 unique_ptr 中是一个令人困惑的额外间接层。

• 从 c++11 和最新版本的 boost 开始，asio 套接字是可移动的。您可以按值返回它们，而不是像我所做的那样传递引用。

• 我注意到您在代码中混合了异常和非异常错误处理。您可能想坚持使用其中之一(在我看来，基于异常的错误处理更简洁，但这不是普遍的看法)。