Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site lsuc.UUCP
Path: utzoo!lsuc!dave
From: dave@lsuc.UUCP (David Sherman)
Newsgroups: pe.cust.bugs
Subject: Re: Edition 7 DBM problem
Message-ID: <631@lsuc.UUCP>
Date: Mon, 29-Apr-85 13:38:18 EDT
Article-I.D.: lsuc.631
Posted: Mon Apr 29 13:38:18 1985
Date-Received: Mon, 29-Apr-85 14:06:09 EDT
References: <26500002@okstate.UUCP>
Reply-To: dave@lsuc.UUCP (David Sherman)
Organization: Law Society of Upper Canada, Toronto
Lines: 12
Summary: xX is a NULL pointer problem

I have run into the xX problem before, on Berkeley Mail
and other code. It occurs when NULL is returned
as a value and then that value is used as a pointer.
On a VAX this is guaranteed to point to 0. On the
Perkin-Elmer it is "undefined", and in practice
points into a part of memory which appears as "xX"
from printf on diagnostics.

Dave Sherman
The Law Society of Upper Canada
-- 
{  ihnp4!utzoo  pesnta  utcs  hcr  decvax!utcsri  }  !lsuc!dave