websocketpp::exception::what() gives unexpected results

[fabioang]

When m_msg is empty what() returns a pointer which is out of scope

    virtual char const * what() const throw() {
        if (m_msg.empty()) {
            return m_code.message().c_str();   // temporary goes out of scope
        } else {
            return m_msg.c_str();
        }
    }

A possible solution could be:

    virtual char const * what() const throw() {
        if (m_msg.empty()) {
            m_msg = m_code.message().c_str();
        }
        return m_msg.c_str();
    }
private:
    mutable std::string m_msg; // added mutable
    lib::error_code m_code;

Regards,
Fabio

[zaphoyd]

This should be fixed on the develop branch now

[zaphoyd]

The fix for this issue is now present in the 0.5.0 release on the master branch.