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
I ran into an issue today where I accidentally ran head within the VM with no arguments, so the program froze trying to read from stdin. I think I waited a minute or two before killing the trace, which made me think that the S2E analysis isn't timing out like I thought it would.
We may want to look into this to see if S2E does in fact enforce a maximum analysis runtime. If it doesn't, we may consider adding it as a new configuration parameter or command line argument.
The text was updated successfully, but these errors were encountered:
I verified that this is occurring. I let a sample run in the background for more than 5 minutes. S2E did not stop the analysis process or shutdown the VM during that time.
We would most likely need to enforce a timeout within the VM itself (via bootstrap.sh) or externally within Python.
To test, I ran:
just new-project head ./test/benchmark/samples/bin/x86/coreutils/head ""
just run head
This will block indefinitely trying to read stdin.
I ran into an issue today where I accidentally ran
head
within the VM with no arguments, so the program froze trying to read fromstdin
. I think I waited a minute or two before killing the trace, which made me think that the S2E analysis isn't timing out like I thought it would.We may want to look into this to see if S2E does in fact enforce a maximum analysis runtime. If it doesn't, we may consider adding it as a new configuration parameter or command line argument.
The text was updated successfully, but these errors were encountered: