mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 14:48:21 +00:00
93a3a11d36
* origin/topic/vern/script-opt-keep-asserts:
ZAM documentation updates for asserts and event handler run-time errors
BTest updates for ZAM support of (optionally) keeping "assert" statements
command-line options for controlling script optimization: keeping asserts, avoiding event handler coalescence
ZAM support for option to not coalesce event handlers
ZAM support for keeping "assert" statements
internal support for script optimization options for keeping asserts, not consolidating event handlers
ZAM operations to support asserts
simplified "assert" by not trying to catch messages that themselves have errors
Fixed some TEST-REQUIRES "${ZEEK_ZAM}" == "1" to use "=" instead to
be /bin/sh compatible.
23 lines
596 B
Text
23 lines
596 B
Text
# A version of uninitialized-local.zeek suitable for ZAM's behavior.
|
|
# @TEST-REQUIRES: test "${ZEEK_ZAM}" = "1"
|
|
# @TEST-EXEC-FAIL: zeek -b %INPUT >out 2>&1
|
|
|
|
event testit() &priority=10
|
|
{
|
|
local my_count: count = 10;
|
|
}
|
|
|
|
event testit()
|
|
{
|
|
# my_string's value occupies same Frame offset as my_count's from above
|
|
# handler, but execution of this handler body should still "initialize"
|
|
# it to a null value instead of referring to a left-over value of my_count.
|
|
local my_string: string;
|
|
local my_vector: vector of string;
|
|
my_vector[0] = my_string;
|
|
}
|
|
|
|
event zeek_init()
|
|
{
|
|
event testit();
|
|
}
|