🚀 go-pugleaf

harris@garfield.catt.ncsu.edu (Michael Harris) writes:
: mn87504@cs.tut.fi (Naatula Mika) writes:
: 
: >I thought that OS/2 could detect writes to non-allocated areas and
: >give me a segmentation fault right away.  Like it usually does. 
: 
: What you have to understand is that the area IS allocated as far as the
: operating system is concerned.  It is allocated to your process.  Since your
: process owns it, the operating system is very happy to let you write there.
: 
: Memory protection in OS/2 protects one process from another... not a process
: from itself.

OS/2 2.0 = Flat memory model
OS/2 1.x = Segmented memory model.

The segmented memory model had some advantages over the flat model. If I
used DosAllocSeg() to create a 20k block and then ran off the end of
it I'd get a segmentation violation as soon as I did that. (As in Win 3.x)

So although the FLAT memory model simplifies programming it hampers
debugging.

Well as they say "You can't have your cake and eat it too"