Vitaly Chipounov

You can use only one core in S2E.

The S2E engine is single-cpu by design. I estimate it would take 6 months full time work to make it multi-cpu. We would need the following: 1. Update the KVM...

Before you embark on a complex task, there may be a simpler thing that would solve your timeout issues, which is to slow down the guest clock. This way, the...

A memory page that contains symbolic data gets a special flag in the TLB. When ld/st see this flag, they eventually execute io_read/write/check, which will then switch to symbolic mode.

Yes, that's right. In normal QEMU, there is ``notdirty_mem_ops`` that handles the first write access to a mapped page to set various dirty bits. S2E builds on top of that...

There are two steps: 1. Convert an address from guest virtual memory to host virtual memory. This is the same as on QEMU. 2. Convert the host virtual memory address...

The S2E engine shouldn't have any issues running FreeBSD or any other x86 OS. However, all the tooling around S2E only supports Linux and Windows. Here's what you could do...

This question is not related to the issue. Please ask on the s2e-dev mailing list.

Partially done in #503

No there isn't, but I would be happy to advise whoever decides to add support for that.