2015-04-05 62 views
0

我一直在尝试运行几个boost :: asio示例。他们编译和链接没有问题,但是当他们尝试在io_service上注册async_accept时,他们正在抛出分段错误。我附上了下面的代码。它没有从boost文档修改过。在Visual Studio 2013 boost :: asio示例代码段错误

// 
// server.cpp 
// ~~~~~~~~~~ 
// 
// Copyright (c) 2003-2014 Christopher M. Kohlhoff (chris at kohlhoff dot com) 
// 
// Distributed under the Boost Software License, Version 1.0. (See accompanying 
// file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) 
// 

#include <ctime> 
#include <iostream> 
#include <string> 
#include <memory> 
#include <boost/bind.hpp> 
#include <boost/asio.hpp> 

using boost::asio::ip::tcp; 
class session { 
public: 
    session(boost::asio::io_service& io_service) 
    : socket_(io_service) {} 

    tcp::socket& socket() { 
    return socket_; 
    } 

    void start() { 
    socket_.async_read_some(boost::asio::buffer(data_, max_length), 
          boost::bind(&session::handle_read, this, 
          boost::asio::placeholders::error, 
          boost::asio::placeholders::bytes_transferred)); 
    } 

    void handle_read(const boost::system::error_code& error, 
        size_t bytes_transferred) { 
    if (!error) { 
     boost::asio::async_write(socket_, 
           boost::asio::buffer(data_, bytes_transferred), 
           boost::bind(&session::handle_write, this, 
           boost::asio::placeholders::error)); 
    } 
    else { 
     delete this; 
    } 
    } 

    void handle_write(const boost::system::error_code& error) { 
    if (!error) { 
     socket_.async_read_some(boost::asio::buffer(data_, max_length), 
           boost::bind(&session::handle_read, this, 
           boost::asio::placeholders::error, 
           boost::asio::placeholders::bytes_transferred)); 
    } 
    else { 
     delete this; 
    } 
    } 

private: 
    tcp::socket socket_; 
    enum { max_length = 1024 }; 
    char data_[max_length]; 
}; 

class server { 
public: 
    server(boost::asio::io_service& io_service, short port) 
    : io_service_(io_service), 
    acceptor_(io_service, tcp::endpoint(tcp::v4(), port)) { 
    session* new_session = new session(io_service_); 
    acceptor_.async_accept(new_session->socket(), 
          boost::bind(&server::handle_accept, this, new_session, 
          boost::asio::placeholders::error)); 
    } 

    void handle_accept(session* new_session, 
        const boost::system::error_code& error) { 
    if (!error) { 
     new_session->start(); 
     new_session = new session(io_service_); 
     acceptor_.async_accept(new_session->socket(), 
          boost::bind(&server::handle_accept, this, new_session, 
          boost::asio::placeholders::error)); 
    } 
    else { 
     delete new_session; 
    } 
    } 

private: 
    boost::asio::io_service& io_service_; 
    tcp::acceptor acceptor_; 
}; 

回溯:

> gryphon.exe!boost::asio::detail::win_iocp_io_service::work_started() Line 96 C++  gryphon.exe!boost::asio::detail::win_iocp_socket_service_base::start_accept_op(boost::asio::detail::win_iocp_socket_service_base::base_implementation_type & impl, bool peer_is_open, boost::asio::detail::socket_holder & new_socket, int family, int type, int protocol, void * output_buffer, unsigned long address_length, boost::asio::detail::win_iocp_operation * op) Line 480 C++ 
    gryphon.exe!boost::asio::detail::win_iocp_socket_service<boost::asio::ip::tcp>::async_accept<boost::asio::basic_socket<boost::asio::ip::tcp,boost::asio::stream_socket_service<boost::asio::ip::tcp> >,boost::_bi::bind_t<void,boost::_mfi::mf2<void,server,session *,boost::system::error_code const &>,boost::_bi::list3<boost::_bi::value<server *>,boost::_bi::value<session *>,boost::arg<1> > > >(boost::asio::detail::win_iocp_socket_service<boost::asio::ip::tcp>::implementation_type & impl, boost::asio::basic_socket<boost::asio::ip::tcp,boost::asio::stream_socket_service<boost::asio::ip::tcp> > & peer, boost::asio::ip::basic_endpoint<boost::asio::ip::tcp> * peer_endpoint, boost::_bi::bind_t<void,boost::_mfi::mf2<void,server,session *,boost::system::error_code const &>,boost::_bi::list3<boost::_bi::value<server *>,boost::_bi::value<session *>,boost::arg<1> > > & handler) Line 487 C++ 
    gryphon.exe!boost::asio::socket_acceptor_service<boost::asio::ip::tcp>::async_accept<boost::asio::ip::tcp,boost::asio::stream_socket_service<boost::asio::ip::tcp>,boost::_bi::bind_t<void,boost::_mfi::mf2<void,server,session *,boost::system::error_code const &>,boost::_bi::list3<boost::_bi::value<server *>,boost::_bi::value<session *>,boost::arg<1> > > >(boost::asio::detail::win_iocp_socket_service<boost::asio::ip::tcp>::implementation_type & impl, boost::asio::basic_socket<boost::asio::ip::tcp,boost::asio::stream_socket_service<boost::asio::ip::tcp> > & peer, boost::asio::ip::basic_endpoint<boost::asio::ip::tcp> * peer_endpoint, boost::_bi::bind_t<void,boost::_mfi::mf2<void,server,session *,boost::system::error_code const &>,boost::_bi::list3<boost::_bi::value<server *>,boost::_bi::value<session *>,boost::arg<1> > > && handler, void * __formal) Line 285 C++ 
    gryphon.exe!boost::asio::basic_socket_acceptor<boost::asio::ip::tcp,boost::asio::socket_acceptor_service<boost::asio::ip::tcp> >::async_accept<boost::asio::ip::tcp,boost::asio::stream_socket_service<boost::asio::ip::tcp>,boost::_bi::bind_t<void,boost::_mfi::mf2<void,server,session *,boost::system::error_code const &>,boost::_bi::list3<boost::_bi::value<server *>,boost::_bi::value<session *>,boost::arg<1> > > >(boost::asio::basic_socket<boost::asio::ip::tcp,boost::asio::stream_socket_service<boost::asio::ip::tcp> > & peer, boost::_bi::bind_t<void,boost::_mfi::mf2<void,server,session *,boost::system::error_code const &>,boost::_bi::list3<boost::_bi::value<server *>,boost::_bi::value<session *>,boost::arg<1> > > && handler, void * __formal) Line 1020 C++ 
    gryphon.exe!server::server(boost::asio::io_service & io_service, short port) Line 75 C++ 
    gryphon.exe!main() Line 32 C++ 
    [External Code] 

我以前得到这个代码工作,但此后重新编译64位提升(地址模型-64)。我认为这是错误的原因,但我不明白Visual Studio或Boost的构建设置足够了解。

编辑: 编译器选项

/GS /analyze- /W3 /Zc:wchar_t /I"src" /I"include" /I"C:\boost\boost_1_55_0" /ZI /Gm /Od /Fd"Debug\vc120.pdb" /fp:precise /D "_CRT_SECURE_NO_DEPRECATE" /D "_WIN32_WINDOWS" /D "WPCAP" /D "WIN32" /D "_DEBUG" /D "_CONSOLE" /errorReport:prompt /WX- /Zc:forScope /RTC1 /Gd /Oy- /MDd /Fa"Debug\" /EHsc /nologo /Fo"Debug\" /Fp"Debug\gryphon.pch" 

连接器选项

/OUT:"C:\Users\USER\Documents\Visual Studio 2013\Projects\gryphon\Debug\gryphon.exe" /MANIFEST /NXCOMPAT /PDB:"C:\Users\USER\Documents\Visual Studio 2013\Projects\gryphon\Debug\gryphon.pdb" /DYNAMICBASE "Ws2_32.lib" "Packet.lib" "wpcap.lib" "kernel32.lib" "user32.lib" "gdi32.lib" "winspool.lib" "comdlg32.lib" "advapi32.lib" "shell32.lib" "ole32.lib" "oleaut32.lib" "uuid.lib" "odbc32.lib" "odbccp32.lib" /DEBUG /MACHINE:X86 /INCREMENTAL /PGD:"C:\Users\USER\Documents\Visual Studio 2013\Projects\gryphon\Debug\gryphon.pgd" /SUBSYSTEM:CONSOLE /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /ManifestFile:"Debug\gryphon.exe.intermediate.manifest" /ERRORREPORT:PROMPT /NOLOGO /LIBPATH:"lib" /LIBPATH:"C:\boost\boost_1_55_0\stage\lib" /TLBID:1 

升压/级/ lib目录包含32位预编译库。希望了解有关32位/ 64位/多线程/静态boost库与Windows运行时库之间差异的任何见解。

+0

快速浏览它看起来很好。尝试一个完整的重建。重新检查所有项目/库共享编译器/链接器选项 – sehe 2015-04-05 18:03:11

+0

重建升级没有任何其他选项。如果这不起作用,我会用这段代码开始一个新的VS项目,看看是否有效。谢谢 – user2411693 2015-04-05 18:13:18

回答

0

得到它的工作。使用默认选项和改变的编译器/连接选项下面的重建加速:(我想删除子系统/ CONSOLE标志是什么让差异)

编译:

/GS /analyze- /W3 /Zc:wchar_t /I"src" /I"include" /I"C:\boost\boost_1_55_0\" /ZI /Gm /Od /sdl /Fd"Debug\vc120.pdb" /fp:precise /D "_CRT_SECURE_NO_DEPRECATE" /D "WPCAP" /D "WIN32" /D "_DEBUG" /D "_CONSOLE" /errorReport:prompt /WX- /Zc:forScope /RTC1 /Gd /Oy- /MDd /Fa"Debug\" /EHsc /nologo /Fo"Debug\" /Fp"Debug\gryphon.pch" 

链接:

/OUT:"C:\Users\USER\Documents\Visual Studio 2013\Projects\gryphon\Debug\gryphon.exe" /MANIFEST /NXCOMPAT /PDB:"C:\Users\USER\Documents\Visual Studio 2013\Projects\gryphon\Debug\gryphon.pdb" /DYNAMICBASE "Ws2_32.lib" "Packet.lib" "wpcap.lib" "kernel32.lib" "user32.lib" "gdi32.lib" "winspool.lib" "comdlg32.lib" "advapi32.lib" "shell32.lib" "ole32.lib" "oleaut32.lib" "uuid.lib" "odbc32.lib" "odbccp32.lib" /DEBUG /MACHINE:X86 /INCREMENTAL /PGD:"C:\Users\USER\Documents\Visual Studio 2013\Projects\gryphon\Debug\gryphon.pgd" /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /ManifestFile:"Debug\gryphon.exe.intermediate.manifest" /ERRORREPORT:PROMPT /NOLOGO /LIBPATH:"lib" /LIBPATH:"C:\boost\boost_1_55_0\stage\lib" /TLBID:1 
+0

子系统_really_在这里不应该有任何区别。这是其中一种设置,仅仅意味着链接上的某些东西,并且_does不需要与所使用的(共享)库相对应,这只是因为子系统不是静态库上的东西,并且不会在主模块上使用(与入口点,即) – sehe 2015-04-05 20:21:16

+0

不知道是否是它,或者如果它是其中一个其他更改/增强重建。如果是重建,我希望有某种链接器错误。我得到的只是随机的seg故障(从CLI运行或在VS调试器中运行)。只是觉得别人可能会遇到这个问题,或者有人可能会在旗帜中看到一些明显的问题原因。 – user2411693 2015-04-05 20:51:24

+0

ABI不兼容将导致[未定义行为](http://en.wikipedia.org/wiki/Undefined_behavior)。不需要诊断,事实上很少有可能。不过,我相信带有-flto的GCC已经引入了一些与ODR相关的警告。 – sehe 2015-04-05 20:52:53