Closed J-jaeyoung closed 1 year ago
You are correct, the runtime environment has no interruption happening. This is done so that you don't burn time fuzzing something that isn't your target (another random process for example).
Technically what you want to do is probably possible but hard to make generic. wtf would need to know the threads of your target and artificially context switch into them. You could imagine forcing a context switch after a maximum of instruction and when the threads yield but it isn't implemented and I haven't played with this idea either. It's always been on the back of my mind though, so if you end up trying to make something work, let me know!
Cheers
Oh, now I clearly understand what's going on. I should experiment more with wtf and try implementing it on weekends.
Thank you for this wonderful project.
Thank you for trying it out 🙏🏽!
Hello, I have tried to discover race condition bugs with wtf. After some experiments with the following sample target, I've concluded bochscpu doesn't emulate timer interrupt, which means that thread-switching doesn't occur at all.
If I understand correctly, wtf cannot detect multithread-related race bugs, is it right? Could kvm or whv be potential solutions for detecting these bugs, or is there any possible workarounds?
Thanks.