-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SymQEMU tests and Dockefile #39
Conversation
…instrumented instructions
Thank you for your interest in the QEMU project. This repository is a read-only mirror of the project's repostories hosted QEMU welcomes contributions of code (either fixing bugs or adding new |
Sorry for the inconvenience, this was closed by a GH action that came from the merge of QEMU, and it seems that while I can unlock I cannot reopen the PR (it seems to be not possible: isaacs/github#361) |
We can do this one before #38, this is a mistake on my side, I will submit a new PR tomorrow |
In fact in the future maybe we should get SymCC to push a docker image (to Docker Hub or GitHub Packages) and use that one, so we don't even recompile it here.
Great, thanks ! |
The goal of this PR is to have an automated testing of SymQEMU that runs it on a known binary and checks that it outputs the expected results.
This is WIP but you can already check what I have.
For now this PR contains the script for running SymQEMU on a simple test program, and a Dockerfile that compiles SymQEMU and runs the test.
Instead of compiling SymCC during the image build, I think it makes more sense to rely on the existing docker image for SymCC and extract from it the needed .so file. This way, if the commands needed for compiling SymCC change in the future, only the Dockerfile of SymCC will need to be updated.