Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/17/84; site hplabs.UUCP
Path: utzoo!utcs!lsuc!pesnta!hplabs!faunt
From: faunt@hplabs.UUCP (Doug Faunt)
Newsgroups: net.arch
Subject: Re: uninitialized data
Message-ID: <2215@hplabs.UUCP>
Date: Mon, 23-Sep-85 16:04:36 EDT
Article-I.D.: hplabs.2215
Posted: Mon Sep 23 16:04:36 1985
Date-Received: Tue, 24-Sep-85 18:42:03 EDT
References: <436@uvm-cs.UUCP> <5600035@uiucdcsb>
Organization: Hewlett Packard Labs, Palo Alto CA
Lines: 13

> 
> One way to trap on uninitialized memory locations is to set the parity bit
> incorrectly for uninitialized locations.  If the location is read before being 
> written, a bad parity interrupt will occur.  The Burroughs stack machines use
> this technique.
> 
> - Arch

This is what the original WATFOR for the 7040/44 did, also.
-- 
  ....!hplabs!faunt	faunt%hplabs@csnet-relay.ARPA
HP is not responsible for anything I say here.  In fact, what I say here
may have been generated by a noisy telephone line.


Brought to you by Super Global Mega Corp .com