This repository contains old exams for the course
For the C questions, the subfolders each hold one or more example solutions, a folder with test cases, and a file called myprogram.c which you can use to write and test your own solution. For the proof questions, both exam questions and answers are given in Dafny.
Found this repository useful? Help out your (future) fellow students by mailing your exam paper to me or sending a pull request. It's up to you to keep this repository up to date!
| 2012 | 2013 | 2014 |
| 2015 | 2015 resit | 2016 |
| 2017 | 2017 resit | 2018 |
| 2018 resit | 2019 | 2019 resit |
| 2020 | 2021 | 2022 |
| 2013 | 2015 | 2016 |
| 2016 resit | 2017 | 2017 resit |
| 2018 | 2018 resit | 2019 |
| 2019 resit | 2020 | 2020 resit |
| 2021 | 2021 resit | 2022 |
| 2023 | 2023 resit | 2024 |
| 2025 | ||
| 2023 | 2023 resit | 2024 |
| 2024 resit | 2025 | |
| 2024 | 2024 resit | 2025 |
You can test your own C code with the test script. The script
compiles your program, runs it on all .in test cases, and compares the
output with the corresponding .out files.
By default you get a clean summary (PASS or FAIL per test case).
If a test fails, and you want to see the difference in expected and actual output, or you want to have extra Valgrind tests, you can use the following options:
--show-diffor-dshows a small preview of the output differences for failed tests, including the first 5 lines of the expected output and the first 5 lines of your actual output (both indented under the test case).--valgrindor-venables Valgrind checks (PASS or FAIL per test case).--show-vgor-eshows Valgrind error details for failed Valgrind checks.--helpor-hprints the full usage message.
If you want to use this script, you basically have two options:
Opening a terminal from the working directory containing your program, the solution, and the folder with the tests, run the below commands.
First, make the script executable:
chmod +x ../../../ctest.shThen run the script by using the following command:
../../../ctest.sh myprogram.cYou can add options before the program file:
../../../ctest.sh --show-diff --valgrind myprogram.cAlternatively, you can add the script to your PATH variable and run it from anywhere. To display the current $PATH, run the following command:
echo $PATHThen, copy the script to one of the folders in $PATH. If you have copied the script to the folder before, the command will simply overwrite the previous version. For example:
sudo cp ctest.sh /usr/bin/Now you can run the script from the directory containing your program and the folder with test cases by using the following command:
ctest.sh myprogram.cYou may also choose to redirect the output to a file, in which case the script automatically disables ANSI colors to render a plain text file:
ctest.sh myprogram.c > results.txtThe folder Functions contains a small C utility library called clib comprising various helpers for arrays, strings, matrices, sorting, searching, etc. This library is intended to be used as a support library for the exercises in this repository.
This library is easy to extend: you can add your own helpers under Functions/src and declare them under Functions/include/clib, rebuild the static library, and all programs in the repo can immediately use the new functionality while the core stays compact and maintainable.
The library is organized as:
- headers in
Functions/include/clib/ - sources in
Functions/src/ - build output in
Functions/build/
You can include the full library with the umbrella header:
#include "../../Functions/include/clib/clib.h"Or include only what you need (for example just integers):
#include "../../Functions/include/clib/integers.h"Available headers include:
clib.h, integers.h, strings.h, sorting.h, searching.h, math.h, memory.h, and macros.h.
The library is built as a static library via the Makefile in the Functions folder. You can build it manually by running make in that folder. This will create the static library file build/libclib.a. However, when you use ctest.sh, and include a header from the library in your program, the script will automatically call the Makefile to build the library if it is not already built.
Some concrete examples of how to use the library can be found in the Functions and Extra-C folders.
All commands were given with Ubuntu in mind. If you are using a different Linux distribution, you may need to change the commands accordingly.
The script was tested on Ubuntu 24.04 LTS, using GCC 14.2.0, and Valgrind 3.22.0.
If you want to compile and test your code manually, you can use the following commands:
gcc -O2 -std=c99 -pedantic -Wall -o a.out myprogram.c -lmvalgrind --leak-check=full ./a.out < tests/1.in-- This will be added later --