State terminating error in S2E

[Mukta Debnath]

Hi,

S2E is terminating all states after generating only one test-case which is the supplied concrete input for the binary. I use the following command:

s2e new_project --image debian-9.2.1-x86_64 -n fft-cwom-sym ./fft.exe -infile ./fft_input.txt

The following screen appears after running "./launch-s2e.sh"

Thanks and Regards,

Mukta

[Vitaly Chipounov]

Hi,

Did you check that the program actually ran in the guest? If you built your binary on Ubuntu 22.04, it will not run on Debian 9, which by the way is not supported anymore. Most recent version of S2E builds Debian 11.

Vitaly

--
You received this message because you are subscribed to the Google Groups "S2E Developer Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to s2e-dev+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/s2e-dev/248df703-a06f-44c5-a809-f06af10ee7c9n%40googlegroups.com.

[Mukta Debnath]

Hello,

My Ubuntu version is 20.04.3 LTS. Which guest image is supported for this from the available images?

Thanks and Regards,

Mukta

To view this discussion on the web visit https://groups.google.com/d/msgid/s2e-dev/CACjSjcssKjGn8owrw42sc_22gO93s9HcLoD7%3Dj3U_N6vDKf%3DZQ%40mail.gmail.com.

[Vitaly Chipounov]

None. S2E builds and runs on Ubuntu 22.04 LTS and Debian 11 (64-bit). Earlier versions may still work, but we do not support them anymore. [1]
You seem to be running a two years old version of S2E since you have Debian 9 guest images. I don't have the resources to support that.

That being said, the same debugging techniques would apply on recent versions as well:
- Enable graphics output (GUI=1 ./launch-s2e.sh)

- Put a sleep at the end of bootstrap.sh to pause execution.

- Start S2E

- Type ctrl+c in the guest to abort execution and drop to the shell.

- Launch your program manually. See if it runs properly and there are no error messages.

In general, your host and the guest may have different standard libraries. If the one on the host is more recent that the one in the guest, the program will not run. Use a docker container on the host with an identical set up as the guest in order to build the program.

Vitaly

[1] https://s2e.systems/docs/s2e-env.html

To view this discussion on the web visit https://groups.google.com/d/msgid/s2e-dev/CAHma1L_OR%3Dhg119TeP8W1qSf5G50dHMJULcortg1K%3DtzqM%3D8yA%40mail.gmail.com.

[Mukta Debnath]

Thank you. I will be following the steps for debugging.

Yes, I am using the old version of S2E since I faced lots of difficulties in installing the latest version in Ubuntu 22.04 with the image compatibility. I will share in different mail. But due to some deadlines I am using the old version for now.

I just came across an error while running S2E with seeds as shown below. Where should the symranges files for the seeds be stored?

Thanks and Regards,

Mukta

To view this discussion on the web visit https://groups.google.com/d/msgid/s2e-dev/CACjSjctddTedFrSJy0OC7o0n2KdBhwRmYLdVEQh-EguuKLZz2A%40mail.gmail.com.

[Vitaly Chipounov]

Hi,

Please run s2e export_project and attach the archive.

Vitaly

To view this discussion on the web visit https://groups.google.com/d/msgid/s2e-dev/CAHma1L8Wfc0NtdEs7cA6i2EmaNYF7APLVk%3DakpGn1Tg%2BQa9Aig%40mail.gmail.com.

[Mukta Debnath]

Hi,

The exported project is shared in google drive with the following link:

https://drive.google.com/file/d/1FCznoKr6WW3K8gW0_kPeG4ehrOZ9KBtm/view?usp=sharing

I used the following command to build the project:

"s2e new_project --use-seeds --image debian-9.2.1-x86_64 -n uart_swm2 ./uart.exe -infile @@"

Thanks and Regards,

Mukta

[Vitaly Chipounov]

Hi,

You need to provide a *.symranges file if you want to make parts of the file symbolic. Without it, it will be fully concrete.

The format is specified here [1].

Vitaly

[1] https://github.com/S2E/s2e/blob/master/guest/common/s2ecmd/symfile.cpp#L98

To view this discussion on the web visit https://groups.google.com/d/msgid/s2e-dev/CAHma1L8Wfc0NtdEs7cA6i2EmaNYF7APLVk%3DakpGn1Tg%2BQa9Aig%40mail.gmail.com.