Path: utzoo!attcan!uunet!wuarchive!rex!rouge!pc!jpd
From: jpd@pc.usl.edu (Dugal James P.)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Turbo C's Run Time Error Messages
Message-ID: <15661@rouge.usl.edu>
Date: 1 Oct 90 21:06:17 GMT
References: <6243@uceng.UC.EDU>
Sender: anon@rouge.usl.edu
Organization: Univ. of Southwestern La., Lafayette
Lines: 30
Originator: jpd@pc.usl.edu

In article <6243@uceng.UC.EDU> dsims@uceng.UC.EDU (david l sims) writes:
>error messages. One particularly annoying message says at the end
>of the program, "null pointer assignment." I have no idea where
...
>messages off? Does TC give any assistance in tracking down this error
>message?

The Turbo C++ helpme!.doc file says:

 Q. How can I find out where my "null pointer assignment" is occurring?
 A. Set a watch on the following expressions:

            *(char *)0,4m
            (char *)4

    Step through the program. When the values change, the just-executed line
    is the one that is causing the problem.

 Q. My program comes up with the message 'Null pointer assignment'
    after it terminates. What does this mean?
 A. Before a small-data model Turbo C++ program returns to DOS, it will
    check to see if the beginning of its data segment has been corrupted.
    This message is to warn you that you have used uninitialized pointers
    or that your program has corrupted memory in some other way.

-- 
-- James Dugal,	N5KNX		Internet: jpd@usl.edu
Associate Director		Ham packet: n5knx@k5arh
Computing Center		US Mail: PO Box 42770  Lafayette, LA  70504
University of Southwestern LA.	Tel. 318-231-6417	U.S.A.