| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Some syscalls expect null-terminated strings while others get lengths.
Be clear about this distinction.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
More useful trace if we mess up args to a syscall and pass a non-pointer
where a pointer is expected.
|
|
|
|
| |
Don't use trace infrastructure if you're just going to immediately exit.
|
| |
|
|
|