wtf: socket.cc `recv()` timeout
I implemented a custom mutator, and it takes about 1~5 mins for one mutate cycle.
When I run wtf with the custom mutator, I get the following error:
Could not receive size (-1)
Receive failed
Is there any part of the code that sets the timeout or flag such as O_NONBLOCK
?
Actually, I already checked O_NONBLOCK
.
int is_block = !(fnctl(Fd, F_GETFL, 0) & O_NONBLOCK);
// Result: 1
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 1
- Comments: 23 (15 by maintainers)
Commits related to this issue
- Make sure immediate_exit is reset before running a testcase (fix #156) — committed to 0vercl0k/wtf by 0vercl0k a year ago
Hmmmm, it is meant to prevent an infinite testcase running and if it hits it should send a timeout status to the server. I might need to check that code then cause it might be a bug in its own 🤔
On Tue, Apr 4, 2023 at 6:27 PM extf33 @.***> wrote:
I’ll try to repro this this weekend then, thanks for all the details!
Cheers
On Fri, Mar 31, 2023 at 3:01 AM extf33 @.***> wrote: