tweaks to BTests for ZAM feature completeness; new ZAM-only btest

testing/btest/language/uninitialized-local.ZAM.zeek

@@ -0,0 +1,23 @@
+# 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();
+	}

testing/btest/language/uninitialized-local.zeek

@@ -1,3 +1,6 @@
+# Not suitable for ZAM since it spots the error at compile time and exits
+# with an error status code.
+# @TEST-REQUIRES: test "${ZEEK_ZAM}" != "1"
 # @TEST-EXEC: zeek -b %INPUT >out 2>&1
 # @TEST-EXEC: TEST_DIFF_CANONIFIER=$SCRIPTS/diff-remove-abspath btest-diff out
 

testing/btest/language/when-unitialized-rhs.zeek

@@ -1,5 +1,6 @@
-# C++-compiled scripts don't check for missing functions - not clear it's
+# Compiled scripts don't fully check for missing functions - not clear it's
 # worth fixing that.
+# @TEST-REQUIRES: test "${ZEEK_ZAM}" != "1"
 # @TEST-REQUIRES: test "${ZEEK_USE_CPP}" != "1"
 # @TEST-EXEC: zeek -b -r $TRACES/wikipedia.trace %INPUT >out 2>&1
 # @TEST-EXEC: TEST_DIFF_CANONIFIER=$SCRIPTS/diff-remove-abspath btest-diff out