You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 16, 2026. It is now read-only.
I'm running around 20 workers with many hprintf calls. Doing this in tmux over ssh on a remote machine.
Sometimes, calls to print in kafl's logging facilities would raise BlockingIOError due to inability to do I/O without blocking. A small issue, but the call is made in the context of a worker. So worker dies.
Catching exception and retrying allowed my setup to work normally - as a quick hack. But I think it is not the optimal way to fix this.
Instead, do you think its possible to make kAFL use standard python logging library? or at least move this things out of worker's context.
I'm running around 20 workers with many
hprintfcalls. Doing this in tmux over ssh on a remote machine.Sometimes, calls to
printin kafl's logging facilities would raiseBlockingIOErrordue to inability to do I/O without blocking. A small issue, but the call is made in the context of a worker. So worker dies.Catching exception and retrying allowed my setup to work normally - as a quick hack. But I think it is not the optimal way to fix this.
Instead, do you think its possible to make kAFL use standard python logging library? or at least move this things out of worker's context.