maps.write_bytes consider allowing a write that cross two maps

[sha0coder]

If a code start writing at the end of a map and continue writting on the beginnig of the next map, that's not logic and it's not allowed on MWEMU, but Windows would allow it (if there is write permission on both maps)

    pub fn write_bytes(&mut self, addr: u64, data: Vec<u8>) {
        //TODO: fix map jump

[acheron2302]

I think this one is hard because you will need to emulate how windows aslr work. But unless there is a program which we can test I don't think we can emulate with that high precision (except for windows xp).

[sha0coder]

yeah, for now I think is more convinient not emulating aslr.
For debugging/emulating/automating having predictable addresses is quite nice.
This is probably more likely process space simulation than emulation.