Remove the forest of special exceptions, and simply log a short
message to the NET logging category when an exception happens during
packet processing. It is not good to panick end users with errors
that any peer can generate (let alone writing to stderr).
@ -3333,32 +3333,10 @@ bool PeerLogicValidation::ProcessMessages(CNode* pfrom, std::atomic<bool>& inter
returnfalse;
if(!pfrom->vRecvGetData.empty())
fMoreWork=true;
}
catch(conststd::ios_base::failure&e)
{
if(strstr(e.what(),"end of data")){
// Allow exceptions from under-length message on vRecv
LogPrint(BCLog::NET,"%s(%s, %u bytes): Exception '%s' caught, normally caused by a message being shorter than its stated length\n",__func__,SanitizeString(strCommand),nMessageSize,e.what());