-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash related to broker python bindings when running zeekctl
#187
Comments
@Neverlord any idea? |
Not yet. I couldn't spot something obvious in the output other than that it seems to die in Broker's |
Here's another thread with people running into the same: https://lists.zeek.org/archives/list/[email protected]/thread/BCAQ4G3HZ244W4EGRVPK4KHER67KCNVH/ Seems like CentOS 8.4 can trigger it pretty readily, where as 8.3 is hit or miss. The current Docker image for CentOS is still 8.3. |
A slightly better stacktrace:
It looks like it might be something with GCC too. It builds and runs fine with Clang 11 on CentOS 8.4, but the default version of GCC (8.4.1) crashes. |
Tried using faulthandler:
|
And one more, just for broker:
|
@grigorescu @timwoj thanks a lot for the input! I can reproduce this on CentOS, but investigating wasn't so straightforward since it won't reproduce with ASAN builds. Judging from traces you've provided (in particular seeing this fail in After patching the singletons out (see #191 and zeek/zeek#1646), it no longer crashes for me (crashes every time when using the |
I ran into this while setting up a Docker configuration to run long-term benchmarks of zeek. Python crashed when running
zeekctl deploy
and while minimizingzeekctl
to a smaller script, it looked like it was the broker bindings causing it to crash. Adding--disable-python
to my zeek build ultimately resolved it but I'm reporting this anyways.Python backtrace from gdb: backtrace.txt
Python verbose output running minimized script: python_verbose.txt
Minimized script: test.py.txt
Dockerfile used for testing: Dockerfile.txt
The text was updated successfully, but these errors were encountered: