Steven Engler
Steven Engler
The current memory blocklet counts shared memory as cached memory. This leads to the blocklet reporting a lower memory usage than expected (by up to 40% on my laptop). This...
In this PR the event processing has been simplified and moved into the host object. Each host's event queue is reference counted and stored by both the host and the...
In general, we'd like Shadow to manage every syscall that a plugin makes. But there may be cases where a user wants to do something that Shadow doesn't support, for...
If a plugin is killed while it has more than one thread, Shadow doesn't correctly detect that the process was killed. Shadow will still report the simulation as successful. Unexpected...
This uses the ["Contributor Covenant"](https://www.contributor-covenant.org/) template, with the following changes: 1. Shortened the 'Enforcement Guidelines' section of code of conduct. — As a small project with few people, I think...
When running a Shadow simulation that uses statically linked binaries, Shadow will fail to interpose processes for those binaries. This can be confusing since the processes will run outside of...
It would be nice if using ctrl-c to stop shadow would flush the log before exiting. Probably would want to handle SIGTERM and SIGHUP as well.
Events for poll and epoll include `EPOLLHUP`/`POLLHUP` and `EPOLLERR`/`POLLERR` to indicate hang up / error conditions on files. Shadow currently only supports `EPOLLIN` and `EPOLLOUT` for level-triggered events, so it...
If a host receives a TCP packet at a port that doesn't have a bound socket (no socket for the 5-tuple), the host just drops the packet without sending an...
While it hasn't been an issue for us, I think it would be good to have a code of conduct document anyways. Two possible options: - adapt Tor's code of...