hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Move assertion after error message

Browse Source 
Logging the internal state before the assertion makes it easier to figure
out why the assertion failed in the first place.
This commit is contained in:
Markus Mäkelä
2019-04-15 12:07:48 +03:00
parent b3399dccc4
commit f6bd9fefa4
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
server/modules/protocol/MySQL/rwbackend.cc
View File

@ -303,8 +303,8 @@ void RWBackend::process_packets(GWBUF* result)
case REPLY_STATE_DONE: case REPLY_STATE_DONE:
// This should never happen // This should never happen
mxb_assert(!true);
MXS_ERROR("Unexpected result state. cmd: 0x%02hhx, len: %u", cmd, len); MXS_ERROR("Unexpected result state. cmd: 0x%02hhx, len: %u", cmd, len);
mxb_assert(!true);
break; break;
case REPLY_STATE_RSET_COLDEF: case REPLY_STATE_RSET_COLDEF: