mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 06:38:20 +00:00
8049d3a002
This patch changes invocations of `spicyz` and similar Spicy tools in tests which perform compilation to use debug mode via passing `-d`. This in turn leads to Spicy compiling generated C++ code in debug as opposed to release mode which typically seems to require less CPU time and RAM. For a local test running with `btest -j 16` and no caching via `HILTI_CXX_COMPILER_LAUNCER` this sped up running of BTests under `spicy/` by about 40s on my machine (120s vs 160s).
37 lines
1 KiB
Text
37 lines
1 KiB
Text
# @TEST-REQUIRES: have-spicy
|
|
#
|
|
# @TEST-EXEC: spicyz -d -o test.hlto spicy/raw-layer.pcap.spicy spicy/raw-layer.pcap.evt
|
|
# @TEST-EXEC: zeek -r ${TRACES}/dns/proto255.pcap test.hlto %INPUT >output
|
|
# @TEST-EXEC: btest-diff output
|
|
|
|
module PacketAnalyzer::SPICY_RAWLAYER;
|
|
|
|
event zeek_init()
|
|
{
|
|
if ( ! PacketAnalyzer::try_register_packet_analyzer_by_name("IP", 255, "spicy_RawLayer") ) # modified trace to have IP proto 255
|
|
print "cannot register raw analyzer on top of IP";
|
|
}
|
|
|
|
event raw::data(p: raw_pkt_hdr, data: string)
|
|
{
|
|
print fmt("MACs: src=%s dst=%s", p$l2$src, p$l2$dst);
|
|
print fmt("IPs : src=%s dst=%s", p$ip$src, p$ip$dst);
|
|
print fmt("raw bytes: %d", |data|);
|
|
}
|
|
|
|
# @TEST-START-FILE spicy/raw-layer.pcap.spicy
|
|
module RawLayer;
|
|
|
|
import zeek;
|
|
|
|
public type Packet = unit {
|
|
data: bytes &eod;
|
|
};
|
|
# @TEST-END-FILE
|
|
|
|
# @TEST-START-FILE spicy/raw-layer.pcap.evt
|
|
packet analyzer spicy::RawLayer:
|
|
parse with RawLayer::Packet;
|
|
|
|
on RawLayer::Packet::data -> event raw::data($packet, self.data);
|
|
# @TEST-END-FILE
|