[Asterisk-code-review] channel: Add assertion to CHECK BLOCKING. (asterisk[master])
Corey Farrell
asteriskteam at digium.com
Sat Jan 27 14:21:41 CST 2018
Hello Jenkins2,
I'd like you to reexamine a change. Please visit
https://gerrit.asterisk.org/8073
to look at the new patch set (#2).
Change subject: channel: Add assertion to CHECK_BLOCKING.
......................................................................
channel: Add assertion to CHECK_BLOCKING.
Throw an assertion if CHECK_BLOCKING is called when blocking is already
enabled. The macro also returns -1 or 0 based on success but nothing
checks the value yet. I'd like to see if the assertions cause issues
for the testsuite before going further or produces FRACK logger
backtraces in production before moving making additional changes.
ASTERISK-27625
Change-Id: Ia6cacc9c862f2653d1b650511725e53e48e8e653
---
M include/asterisk/channel.h
1 file changed, 16 insertions(+), 9 deletions(-)
git pull ssh://gerrit.asterisk.org:29418/asterisk refs/changes/73/8073/2
--
To view, visit https://gerrit.asterisk.org/8073
To unsubscribe, visit https://gerrit.asterisk.org/settings
Gerrit-Project: asterisk
Gerrit-Branch: master
Gerrit-MessageType: newpatchset
Gerrit-Change-Id: Ia6cacc9c862f2653d1b650511725e53e48e8e653
Gerrit-Change-Number: 8073
Gerrit-PatchSet: 2
Gerrit-Owner: Corey Farrell <git at cfware.com>
Gerrit-Reviewer: Jenkins2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-code-review/attachments/20180127/29e2d6e4/attachment.html>
More information about the asterisk-code-review
mailing list