| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 4648 | Kartik Agaram | 2018-10-01 | 1 | -0/+1 |
| | | |||||
| * | 4619 - new syscall: mmap() | Kartik Agaram | 2018-09-29 | 1 | -0/+17 |
| | | |||||
| * | 4614 - redo simulated RAM | Kartik Agaram | 2018-09-29 | 1 | -14/+1 |
| | | | | | | | | | | | | Now simulated 'Memory' isn't just a single flat array. Instead it knows about segments and VMAs. The code segment will always be first, and the data/heap segment will always be second. The brk() syscall knows about the data segment. One nice side-effect is that I no longer need to mess with Memory initialization regardless of where I place my segments. | ||||
| * | 4613 | Kartik Agaram | 2018-09-29 | 1 | -1/+1 |
| | | |||||
| * | 4552 | Kartik Agaram | 2018-09-20 | 1 | -6/+13 |
| | | | | | | More useful trace if we mess up args to a syscall and pass a non-pointer where a pointer is expected. | ||||
| * | 4522 | Kartik Agaram | 2018-08-14 | 1 | -3/+3 |
| | | | | | Don't use trace infrastructure if you're just going to immediately exit. | ||||
| * | 4520 - several syscalls for files | Kartik Agaram | 2018-08-13 | 1 | -0/+78 |
| | | |||||
| * | 4469 | Kartik Agaram | 2018-08-03 | 1 | -0/+32 |