Promethee

Promethee is a project for visualizing interactions between processes, memory, interrupt vectors, registers and much more.
Written by

[Promethee @PrometheeOS]

If you want to make the project grows up, prefer RT to likes.
RT makes the project to be known out of its circle.
That's not my rules, it's X/Twitter ones.

[Promethee @PrometheeOS]

https://t.co/jdDi5GU83D

[Promethee @PrometheeOS]

My allocator is now able to reclaim previously freed blocks

[Promethee @PrometheeOS]

It's now possible to load multiple process from already registered program or edit an existing one and run it as if.

[Promethee @PrometheeOS]

Besides the data segment.
I've added the ability to execute arbitrary programs on the fly.
The next step will be to change memory data while the process runs.🏃‍♂️
Coupled with the breakpoint and the history snapshot, it will give us an excellent debugging tool🔧
RTs for the win😀

[Promethee @PrometheeOS]

Data segment experimentation

[Promethee @PrometheeOS]

A process can now be killed and restart in another PID. ☠ / 🌱

[Promethee @PrometheeOS]

https://t.co/l2yyoKSZF5

[Promethee @PrometheeOS]

A process can now be restarted in another PID.
Please, RT to make this project known :)

[Promethee @PrometheeOS]

At full CPU speed, this more more revealing

[Promethee @PrometheeOS]

Debugging by breakpoint, functional

[Promethee @PrometheeOS]

@kaporos_ I've no idea, maybe @iMilnb , could help you with that.
as Promethee is both the hardware, the microsoftware and a part of the kernel.
The chosen technical solution is to use a set of lines number as breakpoint and cut the execution flow.

[Promethee @PrometheeOS]

The new version includes breakpoints definition

[Promethee @PrometheeOS]

Hi !
I'm Promethee, my story starts with a little question, a quasi insignificant question.
"How can we create an image for a virtual machine using a CI pipeline, especially a Gitlab one?".
This arose a lot of reaction, showing the interest about the subject.

[Promethee @PrometheeOS]

And this is the app in working as it state of development.
pid 0: write data at address 158
pid 1 : create an array in stack memory, calls a function with reference to data, mutate data
pid 2 : allocate and free data in heap