Skip to content
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

chapters/data/memory-security/drills/tasks: Add solutions and checkers #134

Open
teodutu opened this issue Nov 11, 2024 · 1 comment
Open
Labels
area/code Update or new source code support / solution files area/content Content (Markdown) update area/reading Update to reading content area/tasks Update to tasks kind/improve Improve / Update existing content / item topic/data Related to "Data" chapter

Comments

@teodutu
Copy link

teodutu commented Nov 11, 2024

The tasks in the memory-security subchapter [1] require students to make small changes and notice various behaviours. These can be verified via scripts for each individual task.

Each task (except for exec-shellcode [2]) requires the following changes:

  1. Add solution.
  2. Remove the support/ folder and add the generate_skels.py infrastructure to generate the skeletons from the solutions.
  3. Add checker scripts similar to exec-shellcode [3] to each task. Make sure to only place these checkers in the solution/ folder and have them copied to support/ when running make skels.

[1] https://github.com/cs-pub-ro/operating-systems/tree/main/chapters/data/memory-security/drills/tasks
[2] https://github.com/cs-pub-ro/operating-systems/tree/main/chapters/data/memory-security/drills/tasks/exec-shellcode
[3] https://github.com/cs-pub-ro/operating-systems/tree/main/chapters/data/memory-security/drills/tasks/exec-shellcode/support/tests

@teodutu teodutu added kind/improve Improve / Update existing content / item area/code Update or new source code support / solution files topic/data Related to "Data" chapter area/content Content (Markdown) update area/tasks Update to tasks area/reading Update to reading content labels Nov 11, 2024
@teodutu
Copy link
Author

teodutu commented Nov 11, 2024

Also, add instructions about running objdump specifically about using the -M intel arguments to display the Assembly code in the Intel syntax as opposed to the default AT&T.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/code Update or new source code support / solution files area/content Content (Markdown) update area/reading Update to reading content area/tasks Update to tasks kind/improve Improve / Update existing content / item topic/data Related to "Data" chapter
Projects
None yet
Development

No branches or pull requests

1 participant