[Zeek] Segmentation Fault on Zeek 3.0.0

TQ nothinrandom at gmail.com
Fri Sep 27 19:56:55 PDT 2019

Hey Jon,

Thanks for guidance on this!  You are absolutely right.  If I remove "-t
~/Desktop/logs/output.log", then that segmentation fault goes away.  I have
not a clue why as it works fine for 2.6.2.  I thought something was wrong
with the actual code.  Again, thanks for helping out with this!


On Fri, Sep 27, 2019 at 5:16 PM Jon Siwek <jsiwek at corelight.com> wrote:

> On Fri, Sep 27, 2019 at 9:47 AM TQ <nothinrandom at gmail.com> wrote:
> > cd ~/Desktop/logs/ && sudo rm -f *.log && zeek -C -t
> ~/Desktop/logs/output.log -r ~/Desktop/pcap/ testPlugin1_pcap_1.pcapng
> The `-t` option isn't commonly used and could see it accidentally
> breaking without anyone noticing.  It does still seem to work for me,
> but you might try removing it to see if it makes a difference.
> But the best thing would be if you can provide the full directions to
> be able to reproduce the segfault -- e.g. the plugin/script code along
> with pcap and command-line you're using.
> If you can't share those, then next best thing would be if you can run
> in a debugger (gdb, lldb) and share a stack trace of the segfault.
> - Jon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/zeek/attachments/20190927/f7e56b14/attachment.html 

More information about the Zeek mailing list