Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!ub!uhura.cc.rochester.edu!rochester!pt.cs.cmu.edu!b.gp.cs.cmu.edu!Ralf.Brown@B.GP.CS.CMU.EDU
From: Ralf.Brown@B.GP.CS.CMU.EDU
Newsgroups: comp.os.msdos.programmer
Subject: Re: TC 2.0 odd behaviour, me or it ?
Message-ID: <273ff488@ralf>
Date: 13 Nov 90 12:26:32 GMT
Sender: ralf@b.gp.cs.cmu.edu
Organization: Carnegie Mellon University School of Computer Science
Lines: 21
In-Reply-To: <7129@castle.ed.ac.uk>

In article <7129@castle.ed.ac.uk>, djm@castle.ed.ac.uk (D Murphy) wrote:
}I have a program compiled under TC 2.0 which executes perfectly except
}that it generates a Null pointer assignment AFTER the last instruction
}(as determined by putting a puts() in and getting the error message
}after the intentonal one).
}
}Anyone know why this might be happening ?

In small-data models (tiny, small, medium), the runtime code contains a special
check in the exit code to see whether your program has stored anything through
a NULL pointer.  If you get the message, it means that your program did not
execute perfectly, even though it appeared to do so.  If you change to a large
data model, you will most likely crash your system when you run the program,
because a NULL pointer will then point at the interrupt vector table in low
memory.

--
UUCP: {ucbvax,harvard}!cs.cmu.edu!ralf -=- 412-268-3053 (school) -=- FAX: ask
ARPA: ralf@cs.cmu.edu  BIT: ralf%cs.cmu.edu@CMUCCVMA  FIDO: 1:129/3.1
Disclaimer?    |   I was gratified to be able to answer promptly, and I did.
What's that?   |   I said I didn't know.  --Mark Twain