Error

[Teicu]

Hi Do you have any idea why I get this error when the tool finishes scanning?

[17:17:45] [INFO] Scan is completed root@Pentest vulcat % /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 1 leaked semaphore objects to clean up at shutdown warnings.warn('resource_tracker: There appear to be %d '

[CLincat]

I looked it up and found that it was a "Segmentation Fault using Python Shared Memory": https://stackoverflow.com/questions/63713241/segmentation-fault-using-python-shared-memory

Since I did not experience this problem, it is difficult to fix this error with vulcat, which you can try to fix using:

1. Change the version of Python;
2. Add the value "ignore:semaphore_tracker:UserWarning" to the environment variable "PYTHONWARNINGS", This may be able to ignore the error. This is an example of Linux setting environment variables:

export PYTHONWARNINGS='ignore:semaphore_tracker:UserWarning'

---

我查阅了相关资料，发现这是一个“Python共享内存的段错误”，相关资料： https://stackoverflow.com/questions/63713241/segmentation-fault-using-python-shared-memory

由于我没有遇到这个问题，所以通过vulcat来修复这个错误较为困难，您可以使用以下方式尝试解决：

1. 更换Python的版本;
2. 将值"ignore:semaphore_tracker:UserWarning"添加到环境变量"PYTHONWARNINGS"当中，这样也许可以忽略这个错误。 这是Linux设置环境变量的示例：

export PYTHONWARNINGS='ignore:semaphore_tracker:UserWarning'

------------------ 原始邮件 ------------------ 发件人: "CLincat/vulcat" @.>; 发送时间: 2022年10月18日(星期二) 晚上10:25 @.>; @.***>; 主题: [CLincat/vulcat] Error (Issue #2)

Hi Do you have any idea why I get this error when the tool finishes scanning?

[17:17:45] [INFO] Scan is completed @.*** vulcat % /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 1 leaked semaphore objects to clean up at shutdown warnings.warn('resource_tracker: There appear to be %d '

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>