The simulator (c) is written in a way that requires an insane amount of memory to run -- it's slow too, and not very robust.
Currently, the simulator is experiencing some issue (on my laptop where theres limited RAM and CPU) where it stalls with no error, likely out of memory or too much file I/O.
Also, registering SIGINT makes the process very annoying to kill when it stalls.
A list of fixes that would be nice:
Rewrite simulator.c to make file IO more robust (stop using syscalls like write(), there are libraries (fprintf()) for that!)
Make simulator.c more robust to errors and stalls.
simulator.c can use higher-level C FILE APIs (and other higher level standard library tools)
Rewrite the python portion to use better python practices (e.g. subprocess.Popen() instead of os.system() and actual error handling)
The simulator (c) is written in a way that requires an insane amount of memory to run -- it's slow too, and not very robust. Currently, the simulator is experiencing some issue (on my laptop where theres limited RAM and CPU) where it stalls with no error, likely out of memory or too much file I/O. Also, registering SIGINT makes the process very annoying to kill when it stalls.
A list of fixes that would be nice:
simulator.c
to make file IO more robust (stop using syscalls likewrite()
, there are libraries (fprintf()
) for that!)simulator.c
more robust to errors and stalls.simulator.c
can use higher-level C FILE APIs (and other higher level standard library tools)subprocess.Popen()
instead ofos.system()
and actual error handling)dm me for questions and concerns T's and G's