mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 06:38:20 +00:00
f050d96503
The core.file-analyzer-violation test showed that it's possible to create new threads (log writers) when Zeek is in the process of terminating. This can result in the IO manager's deconstructor deleting IO sources for threads that are still running. This is sort of a scripting issue, so for now log a reporter warning when it happens to have a bit of a bread-crumb what might be going on. In the future it might make sense to plug APIs with zeek_is_terminating(). |
||
|---|---|---|
| .. | ||
| .stderr | ||
| .stdout | ||
| files.log | ||