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
That's exactly what happens. It basically just finds the most performant program that segfaults, but it will happily spend some time doing this. I'm tried of forgetting to double-check this :P
(edit: in particular, it likes to spend time doing loop optimizations: can I move the segfault out of the loop, and then shortcut the loop itself? lol)
Ok, that sounds right. Your original message said this would be a common way for search to "fail", which is what surprised me. I expected search to "succeed", but in a useless way (with a program that always segfaults).
Have stoke print a big warning if the target always segfaults on its inputs. This is a common reason for a search to fail.
The text was updated successfully, but these errors were encountered: