You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
net: Log to net category for exceptions in ProcessMessages
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).
Copy file name to clipboardExpand all lines: src/net_processing.cpp
+3-25Lines changed: 3 additions & 25 deletions
Original file line number
Diff line number
Diff line change
@@ -3333,32 +3333,10 @@ bool PeerLogicValidation::ProcessMessages(CNode* pfrom, std::atomic<bool>& inter
3333
3333
returnfalse;
3334
3334
if (!pfrom->vRecvGetData.empty())
3335
3335
fMoreWork = true;
3336
-
}
3337
-
catch (const std::ios_base::failure& e)
3338
-
{
3339
-
if (strstr(e.what(), "end of data")) {
3340
-
// Allow exceptions from under-length message on vRecv
3341
-
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());
0 commit comments