Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!att!mcdchg!ddsw1!karl
From: karl@ddsw1.MCS.COM (Karl Denninger)
Newsgroups: news.software.b
Subject: Re: dbz caveat
Summary: I'm running Xenix, and compiled without optimization!
Keywords: dbz runtime
Message-ID: <1989Oct12.155301.7681@ddsw1.MCS.COM>
Date: 12 Oct 89 15:53:01 GMT
References: <1139@svx.SV.DG.COM> <1989Sep26.223014.13868@ddsw1.MCS.COM> <9668@b-tech.ann-arbor.mi.us> <6512@ficc.uu.net>
Reply-To: karl@ddsw1.MCS.COM (Karl Denninger)
Organization: Macro Computer Solutions, Inc., Mundelein, IL
Lines: 23

In article <6512@ficc.uu.net> karl@ficc.uu.net (Karl Lehenbauer) writes:
>>>Dbz also appears to have a nasty habit of not noticing if you have a
>>>duplicate under some conditions.  That is, articles which are still in the
>>>history file at times show up again if they are received twice!
>
>Beware that under Sys V/386, the C optimizer breaks dbz, at least under 3.0.
>The misbehavior is dbz saying articles are not duplicate that actually are,
>and the history file is made to be sick-looking.

Ok... but I'm running Xenix 2.3.2!

And yes, I compiled that module (by hand) without optimization.

Any other good guesses?

It is STILL happening, even now that I have turned up the hash value to
something rediculous (but still a prime like it says).

--
Karl Denninger (karl@ddsw1.MCS.COM, <well-connected>!ddsw1!karl)
Public Access Data Line: [+1 312 566-8911], Voice: [+1 312 566-8910]
Macro Computer Solutions, Inc.		"Quality Solutions at a Fair Price"