vasoll@okstate.UUCP (04/29/85)
Are there any known bugs/fixes to the DBM library that was supplied with
Edition 7? We are having rather strange problems with an application that
tries to store() records with zero length value components. When the
program fetch()es the record in question it gets some kind of wierd pointer
(prints as xX in a printf) as the returned value. This may not be a
*bug*, but is at least inconsistant with the (* shudder *) Berkeley system
that the application was developed on. Any help in tracking this down
will be greatly appreciated.
[ WARNING: The "Path:" address of this article will be messed up. Please
route your response by hand! ]
Thanks,
Mark Vasoll
Department of Computing and Information Sciences
Oklahoma State University
UUCP: {cbosgd, ea, ihnp4, isucs1, mcvax, pesnta, uokvax}!okstate!vasoll
ARPA: vasoll%okstate.csnet@csnet-relay.arpadave@lsuc.UUCP (David Sherman) (04/29/85)
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