Stas Sergeev

I just want to find some consistent solution. Previously, because the faults are rare, I wanted to just use e_invalidate manually in a few places. But you want to build...

Off-topic: https://www.youtube.com/watch?v=KRLm4mKhUVU Though I think it is some kind of trolling, not a real review of dosemu2. :)

But read_byte(), memcpy_* and all that - use aliased pointers normally. If you force them to always unprotect, then these cases where unprotect is not needed (because the protection can...

But is also either you hit code or not. I.e. its not just one case. The fact that it is treated as one, bothers me. Unnecessary unprotects.

Of course perhaps you mean that 2.d w/o code hit almost never happens? (insert 2.d after word "but" in my prev msg)

Maybe you meant the later, but your patches suggest you had data and code mixed in. Or was it not the case?

So what are you going to do with linear2unix then? Completely ban? I think I much rather need to see the size of the patch for that, than any fault...

Yes, the attempt to ban linear2unix will likely be comparable to mem_base32 macrosifying, which took a few years. But at least in case of mem_base32 everyone was confident this is...

So given that cw extender uses code/data mix (and I really think other "people" do too, just not so frequently as in real mode), I suppose even if you ban...

> I am happy about 2.b. for sure, however do note that SEL_ADR_X is also > used for read-addresses and sometimes it uses strcmp on those. Yes, I think the...