Solved console format issues

labs/lab-01/tasks/len-xor/README.md

@@ -44,7 +44,7 @@ Use pointer operations and bitwise operations as much as possible!
 To test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/len-xor/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-01/tasks/mirror/README.md

@@ -25,7 +25,7 @@ The `mirror` function should perform an **in-place** reversal of the characters
 To test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/mirror/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-01/tasks/odd-even/README.md

@@ -26,7 +26,7 @@ Traverse an array of 32-bit integers using pointer operations and display the ev
 To test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/odd-even/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-01/tasks/rotations/README.md

@@ -25,7 +25,7 @@ Implement left and right rotations for 32-bit integers in C.
 To test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/rotations/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-02/tasks/delete_first/README.md

@@ -21,7 +21,7 @@ Given a string and a pattern, implement the `delete_first(char *s, char *pattern
 To test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/delete_first/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-02/tasks/find_max/README.md

@@ -22,7 +22,7 @@ compare(const void *a, const void *b)
 To test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/find_max/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-02/tasks/iterate/README.md

@@ -37,7 +37,7 @@ Iterate through the addresses in `v` byte by byte, two bytes at a time, four byt
 To test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/iterate/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-02/tasks/pixels/README.md

@@ -47,7 +47,7 @@ p.b = 0.11 * p.b;
 To test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/pixels/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-02/tasks/pointers/README.md

@@ -12,7 +12,7 @@ Implement the functions [`memcpy()`](http://www.cplusplus.com/reference/cstring/
 To test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/pointers/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-03/tasks/binary_search/README.md

@@ -28,7 +28,7 @@ The skeleton for the code is in `binary_search/support/binary_search.c`.
 To test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/binary_search/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-03/tasks/vector_max/README.md

@@ -28,7 +28,7 @@ The skeleton for the code is in `vector_max/support/vector_max.c`.
 To test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/vector_max/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-04/tasks/cf-of/README.md

@@ -18,7 +18,7 @@ Using the `add` instruction on the `al` register:
 To test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/cf-of/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-04/tasks/conditional-jumps/README.md

@@ -31,7 +31,7 @@ Avoid infinite looping.
 To test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/conditional-jumps/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-04/tasks/fibonacci/README.md

@@ -18,7 +18,7 @@ Calculate the Nth Fibonacci number, where N is given through the `rcx` register.
 To test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/fibonacci/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-04/tasks/grumpy-jumps/README.md

@@ -18,7 +18,7 @@ Modify the source so that the wrong message is not displayed anymore.
 To test the implementation, enter the `tests/` directory and run:
 
 ```console
-./run_all_tests.sh
+student@hsi:~/.../tasks/grumpy-jumps/tests$ ./run_all_tests.sh
 
 test_display_right               ........................ passed ...  50
 test_display_only_right          ........................ passed ...  50

labs/lab-04/tasks/min/README.md

@@ -12,7 +12,7 @@ Calculate the minimum of the numbers in 2 registers (`r9` and `r10`) using a com
 To test the implementation, enter the `tests/` directory and run:
 
 ```console
-./run_all_tests.sh
+student@hsi:~/.../tasks/min/tests$ ./run_all_tests.sh
 
 test_use_compare                 ........................ passed ...  10
 test_use_jump                    ........................ passed ...  10

labs/lab-04/tasks/sets/README.md

@@ -45,7 +45,7 @@ Perform the union of the two sets.
 To test the implementation, enter the `tests/` directory and run:
 
 ```console
-./run_all_tests.sh
+student@hsi:~/.../tasks/sets/tests$ ./run_all_tests.sh
 
 test_reunion                     ........................ passed ...  10
 test_add_value_in_first_set      ........................ passed ...  20

labs/lab-05/tasks/div/README.md

@@ -50,7 +50,7 @@ The divisor is passed as an argument to the `div` mnemonic.
 To test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/div/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-05/tasks/mul/README.md

@@ -66,7 +66,7 @@ You'll need to multiply:
 To test the implementation, enter the tests/ directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/mul/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-05/tasks/sum-array/README.md

@@ -62,7 +62,7 @@ big_qword_array dq 9223372036854775800, 8223372036854775800, 7223372036854775800
 To test the implementation, enter the tests/ directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/sum-array/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-05/tasks/sum-squared/README.md

@@ -30,7 +30,7 @@ Therefore, you cannot easily use the `rax` register to store the sum of squares.
 To test your implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/sum-squared/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-05/tasks/vec-count-if/README.md

@@ -34,7 +34,7 @@ For negative numbers, sign extension should be performed; it would work without
 To test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/vec-count-if/tests$ make check
 ```
 
 In order to get the points, you should have a single line of output with

labs/lab-06/tasks/fibonacci/README.md

@@ -12,7 +12,7 @@ The sum of the first 9 numbers is 54.
 To test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/fibonacci/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-06/tasks/find-substring/README.md

@@ -26,7 +26,7 @@ Substring found at index: <N>
 To test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/find-substring/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-06/tasks/getters-setters/README.md

@@ -32,7 +32,7 @@ Follow the comments marked with **TODO**.
 To test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/getters-setters/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-06/tasks/mul-arrays/README.md

@@ -24,7 +24,7 @@ Therefore, the result is stored on two bytes.
 To test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/mul-arrays/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-06/tasks/print-structure/README.md

@@ -25,7 +25,7 @@ Do not modify the structure in the `.data` section, you need to use code to modi
 To test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/print-structure/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-08/guides/disassembling-c/README.md

@@ -67,7 +67,7 @@ where `<path-to-obj-file>` is the path to the object file `test.o`.
 Afterwards, you'll see an output similar to the following:
 
 ```console
-$ objdump -M intel -d test.o
+student@hsi:~/.../guides/disassembling-c/support$ objdump -M intel -d test.o
 
 test.o:     file format elf64-x86-64
 

labs/lab-08/tasks/print-rev-string/README.md

@@ -81,19 +81,19 @@ After you consider your implementation complete, it is recommended to first run
 In order to do so, enter the `support/` directory and run:
 
 ```console
-make
+student@hsi:~/.../tasks/print-rev-string/support$ make
 ```
 
 If your code successfully compiled, you can then run the binary like so:
 
 ```console
-./print_reverse_string
+student@hsi:~/.../tasks/print-rev-string/support$ ./print_reverse_string
 ```
 
 To fully test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/print-rev-string/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-08/tasks/rot13/README.md

@@ -35,19 +35,19 @@ After you consider your implementation complete, it is recommended to first run
 In order to do so, enter the `support/` directory and run:
 
 ```console
-make
+student@hsi:~/.../tasks/rot13/support$ make
 ```
 
 If your code successfully compiled, you can then run the binary like so:
 
 ```console
-./rot13
+student@hsi:~/.../tasks/rot13/support$ ./rot13
 ```
 
 To fully test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/rot13/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-08/tasks/string-print-len/README.md

@@ -31,19 +31,19 @@ After you consider your implementation complete, it is recommended to first run
 In order to do so, enter the `support/` directory and run:
 
 ```console
-make
+student@hsi:~/.../tasks/string-print-len/support$ make
 ```
 
 If your code successfully compiled, you can then run the binary like so:
 
 ```console
-./print_string_length
+student@hsi:~/.../tasks/string-print-len/support$ ./print_string_length
 ```
 
 To fully test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/string-print-len/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-08/tasks/string-print/README.md

@@ -19,19 +19,19 @@ After you consider your implementation complete, it is recommended to first run
 In order to do so, enter the `support/` directory and run:
 
 ```console
-make
+student@hsi:~/.../tasks/string-print/support$ make
 ```
 
 If your code successfully compiled, you can then run the binary like so:
 
 ```console
-./print_string
+student@hsi:~/.../tasks/string-print/support$ ./print_string
 ```
 
 To fully test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/string-print/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-08/tasks/sum7/README.md

@@ -17,19 +17,19 @@ After you consider your implementation complete, it is recommended to first run
 In order to do so, enter the `support/` directory and run:
 
 ```console
-make
+student@hsi:~/.../tasks/sum7/support$ make
 ```
 
 If your code successfully compiled, you can then run the binary like so:
 
 ```console
-./sum7
+student@hsi:~/.../tasks/sum7/support$ ./sum7
 ```
 
 To fully test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/sum7/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as:

labs/lab-08/tasks/to-upper/README.md

@@ -34,19 +34,19 @@ After you consider your implementation complete, it is recommended to first run
 In order to do so, enter the `support/` directory and run:
 
 ```console
-make
+student@hsi:~/.../tasks/to-upper/support$ make
 ```
 
 If your code successfully compiled, you can then run the binary like so:
 
 ```console
-./to_upper
+student@hsi:~/.../tasks/to-upper/support$ ./to_upper
 ```
 
 To fully test the implementation, enter the `tests/` directory and run:
 
 ```console
-make check
+student@hsi:~/.../tasks/to-upper/tests$ make check
 ```
 
 In case of a correct solution, you will get an output such as: