On Thu, Nov 01, 2007 at 10:40:06PM -0500, Anton Tilstra wrote: > > I don't think it's a hardware issue, since we're using the same > > binaries on three different 64 bit SuSE Linux 10.2 boxes, and they > > all give the same symptom. > > I didn't realize you were running 3 machines exhibiting the same issue, > sorry if I missed that. This would indeed mean it's not a hardware > issue, of course.
No, my bad, I didn't mention that. > > > One thing that comes to mind in that department is a compiler issue > > > (not my first guess, but who knows), assuming I'm understanding > > > correctly that you've compiled it yourself on this machine. If so, > is > > > there a 64 bit SuSE package of DSPAM you could try to run? This > would > > > of course be pretty involved, so I don't think I would do that on a > > > production box. > > > > To my knowledge there's no dspam rpm package available for these > > platforms, that's why we built our own. Also, we do a 32 bit build > > as well, and that one works just fine. > > That would mean you are using a different compiler on the 32 bit > platform, correct? (different binary, even if compiled from the same > source.) Still a long shot, but if there's not much else to go on, I > would still try out a different compiler, or different version at least. Yes, I guess. We're using stock SuSE Linux 10.2 environment including compiler and linker, on both 32 and 64 bit. > Failing that, have you ran any other (previous) versions of DSPAM at any > point? Yes, 32 bit, and successfully so. I'm going to try to use the 32 bit binary on the 64 bit platform and see how that goes. > I'm afraid that's all I can think of at the moment... That's fine, thanks. /L
