Skip to content
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

fix: always occur signal 31 when executing C-based program #63

Merged
merged 1 commit into from
Jan 20, 2022

Conversation

mansukim1125
Copy link
Contributor

Description

I realized that every time I run a C-based program, I always get signal 31. When I searched, I found that other people were experiencing the same issue, and syscall 17 (pread64) was mentioned as the cause. Therefore, we would like to address this issue by adding pread64 to syscalls_whitelist in src/rules/c_cpp.c.

References:

Fixes #39 #46 #47 #54 #58

Type of change

  • Bug fix (non-breaking change which fixes an issue)

@mansukim1125 mansukim1125 marked this pull request as ready for review January 19, 2022 16:06
@virusdefender virusdefender merged commit 016653c into QingdaoU:newnew Jan 20, 2022
@mansukim1125 mansukim1125 deleted the seccomp_signal31 branch January 20, 2022 04:45
@mansukim1125 mansukim1125 restored the seccomp_signal31 branch January 20, 2022 05:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Python writing file returns Runtime Error in File IO mode
2 participants