zagros

a simple operating system from scratch.

prerequisites

• bear
• as
• gcc
• qemu(or virtualbox or bochs)

optional

diff tools

• gitk
• meld

documentation

• doxygen

static analyzers

• cppcheck
• frama-c
• splint

code coverage

• kcov

memory analyzer

• valgrind(memcheck)
• callgrind
• cachegrind
• kcachegrind
• helgrind
• massif

utils

• scc
• fzf
• ambr
• neovim

binary utils

• addr2line
• nm
• objdump
• readelf
• size
• strings

libs

• man-pages-devel man <method>
• libsanitizer-devel
• libsanitizer-devel-32bit

build/run/test

./p

todo

tools

• setup binary analysis tools. (integration with p)
  • "ldd"
  • "objdump"
  • "strings"
  • "nm"
  • "readelf"
  • "addr2line"
  • "size"
  • "file"
• setup util tools. (integration with p)
  • "scc"
• setup doxygen. (integration with p)
• setup clove-unit library. (integration with p)
• setup cppcheck as static-analyzer. (integration with p)
  • setup ale plugin for neovim. (integration with p)
• setup frama-c as static-analyzer. (integration with p)
• setup code coverage. (integration with p)
  • kcov
• setup valgrind. (integration with p)
  • memcheck.
  • callgrind.
  • cachegrind
  • kcachegrind
  • helgrind
  • massif
• setup github actions.
  • create workflow to generate docs using doxygen and push them to: https://github.com/LinArcX/zagr.os
  • run doxygen after each commit.
  • build and run unit-tests for each commit. (when only unit_tests/* files changes)
• create github page.
  • create a home pages contains: 1. doxygen report 2. unit-test results.
  • host doxygen results on it.
  • host unit-tests results on it.
  • host test coverage results on it.

zagros

• strings util.
• minimal c library.
• interrupts.
• keyboard.
• mouse.
• system calls.
• graphic mode.
• create GUI toolkit.
• multi-tasking.
• hard drives.
• networking.

features will not be included in zagros

• dynamic memory management: it makes software unpredictable and non deterministic.