izaya
/
collapseos
mirror of https://github.com/hsoft/collapseos.git
1
0
Fork 0
Code Issues Releases Wiki Activity
collapseos/cvm
History
Virgil Dupras ba8a9c2647 cvm: initialize memory with random garbage 
This should help spot bugs due to bad initialization.
 		2020-08-15 14:24:02 -04:00
..
.gitignore cvm: bootstraps itself! 2020-06-26 18:58:02 -04:00
Makefile cvm: remove makefile duplicate recipe 2020-06-30 10:29:06 -04:00
README.md emul: build from "cvm" instead of from itself 2020-06-26 22:08:45 -04:00
avra.sh move avra.sh from emul to cvm 2020-06-27 07:32:19 -04:00
forth.bin cvm: implement stack overflow error condition 2020-08-07 21:57:25 -04:00
forth.c Add a C implementation of native words 2020-06-26 15:50:13 -04:00
stage.c cvm: bootstraps itself! 2020-06-26 18:58:02 -04:00
vm.c cvm: initialize memory with random garbage 2020-08-15 14:24:02 -04:00
vm.h cvm: implement stack overflow error condition 2020-08-07 21:57:25 -04:00
xcomp.fs cvm: initialize memory with random garbage 2020-08-15 14:24:02 -04:00
zasm.sh Move zasm.sh from emul to cvm 2020-06-27 07:44:43 -04:00

README.md

C VM

This is a C implementation of Collapse OS' native words. It allows Collapse OS to run natively on any POSIX environment.

Requirements

You need ncurses to build the forth executable. In debian-based distros, it's libncurses5-dev.

Build

Running make will yield forth and stage executables.

Usage

To play around Collapse OS, you'll want to run ./forth. Type 0 LIST for help.

The program is a curses interface with a limited, fixed size so that it can provide a AT-XY interface.

You can get a REPL by launching the program with rlwrap(1) like this:

rlwrap -e '' -m -S '> ' ./forth /dev/stdin

Problems?

If the forth executable works badly (hangs, spew garbage, etc.), it's probably because you've broken your bootstrap binary. It's easy to mistakenly break. To verify if you've done that, look at your git status. If forth.bin is modified, try resetting it and then run make clean all. Things should go better afterwards.

A modified blkfs can also break things (although even with a completely broken blkfs, you should still get to prompt), you might want to run make pack to ensure that the blkfs file is in sync with the contents of the blk/ folder.

If that doesn't work, there's also the nuclear option of git reset --hard and git clean -fxd.

If that still doesn't work, it might be because the current commit you're on is broken, but that is rather rare: the repo on Github is plugged on Travis and it checks that everything is smooth.