Path: utzoo!attcan!uunet!know!sdd.hp.com!uakari.primate.wisc.edu!uflorida!gatech!purdue!sage.cc.purdue.edu!rusbara2
From: rusbara2@sage.cc.purdue.edu (Bob Rusbasan)
Newsgroups: comp.os.msdos.programmer
Subject: Re: TC 2.0 odd behaviour, me or it ?
Message-ID: <5068@sage.cc.purdue.edu>
Date: 13 Nov 90 00:21:38 GMT
References: <7129@castle.ed.ac.uk>
Reply-To: rusbara2@sage.cc.purdue.edu (Bob Rusbasan)
Organization: Purdue University
Lines: 16

In article <7129@castle.ed.ac.uk> djm@castle.ed.ac.uk (D Murphy) writes:
>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).

If this isn't in the faq, could someone put it there?  I don't know
if this is the same guy, but I've seen this twice today.

What happens is after running the program it checks the data at the
beginning of it.  If it has been corrupted (usually by writing to
address 0, or NULL) it gives you the error message.  Find where you
write to a NULL pointer, and fix it.

See comp.lang.c. for a more detailed post (I don't feel like going
through all of it twice, and this should suffice for the most part).