Mirror/zeek
1
0
Fork 0
mirror of https://github.com/zeek/zeek.git synced 2025-10-02 06:38:20 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Stmt: Rework assertion hooks break semantics

Browse source 
Using break in either of the hooks allows to suppress the default reporter
error message rather than suppressing solely based on the existence of an
assertion_failure() handler.
This commit is contained in:
Arne Welzel 2023-06-13 15:23:45 +02:00
parent 25ea678626
commit 0b0f6e509f
9 changed files with 40 additions and 26 deletions
Download patch file Download diff file Expand all files Collapse all files

15
scripts/base/init-bare.zeek
View file

@ -944,11 +944,10 @@ type Backtrace: vector of BacktraceElement;
## A hook that is invoked when an assert statement fails.
##
## If no such hook is implemented, a default reporter error message is
## logged similar to how scripting errors are reported.
##
## If assertion_failure hook handlers exist, the default reporter error
## message is suppressed to allow for customized error messaging.
## By default, a reporter error message is logged describing the failing
## assert similarly to how scripting errors are reported after invoking
## this hook. Using the :zeek:see:`break` statement in an assertion_failure
## hook handler allows to suppress this message.
##
## cond: The string representation of the condition.
##
@ -964,7 +963,11 @@ type assertion_failure: hook(cond: string, msg: string, bt: Backtrace);
##
## This is a potentially expensive hook meant to be used by testing
## frameworks to summarize assert results. In a production setup,
## this hook is likely deterimental to performance.
## this hook is likely detrimental to performance.
##
## Using the :zeek:see:`break` statement within an assertion_failure hook
## handler allows to suppress the reporter error message generated for
## failing assert statements.
##
## result: The result of evaluating **cond**.
##