Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!hplabs!hpda!hpcupt1!jonb
From: jonb@hpcupt1.cup.hp.com (Jon Bayh)
Newsgroups: comp.sys.hp
Subject: Re: $bozoword in /hp-ux
Message-ID: <67870003@hpcupt1.cup.hp.com>
Date: 11 Mar 91 19:42:29 GMT
References: <1991Mar7.044007.8938@nmt.edu>
Organization: Hewlett Packard, Cupertino
Lines: 24

> From: schlake@nmt.edu (Schlake)
> 
> $bozoword           |   1421312|static|data   |$DATA$
> iodc_write_buffer   |   1421376|extern|data   |$DATA$
> 
> 1421376-1421312=64      (I checked for other variables in the area)
> 
> Obviously not a 'word' word, so its gotta be a text string.  I wrote a
> quick program to print out the value contained by $bozoword:

Well, I hate to spoil a good mystery, but this question is obviously
of such a critical nature that I feel obliged to comment on it. :-)

The variable $bozoword actually is declared as a word in initialized data.
The problem is that it is the last piece of data in the module that it
is compiled into, and the next module allocates "iodc_write_buffer".  For
various I/O reasons, iodc_write_buffer is defined to be aligned on a
64-byte boundary.  Because $bozoword didn't happen to end on a 64 byte
boundary, padding of zeros are inserted between the two until the alignment
is correct.  $bozoword is an old, old variable in a section of code that
really isn't of much interest to most customers.

			Jon Bayh, UKL
			jonb@hpda