From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from relay1.UU.NET ([192.48.96.5]) by hawkwind.utcs.toronto.edu with SMTP id <2763>; Mon, 15 Feb 1993 20:26:24 -0500 Received: from cygnus.com by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA08637; Mon, 15 Feb 93 20:26:07 -0500 Received: from localhost.cygnus.com by cygnus.com (4.1/SMI-4.1) id AA15916; Mon, 15 Feb 93 17:26:07 PST Message-Id: <9302160126.AA15916@cygnus.com> To: Chris Siebenmann Cc: sam-fans@hawkwind.utcs.toronto.edu Subject: Re: sam on DEC OSF/1 Alpha? In-Reply-To: Your message of "Mon, 15 Feb 93 19:33:44 EST." <93Feb15.193359est.2763@hawkwind.utcs.toronto.edu> Date: Mon, 15 Feb 1993 20:26:07 -0500 From: brendan@cygnus.com > Well, thanks to John Mackin, I now have the problem identified. > Pointers in DEC Alpha OSF/1 are 64 bits (as is 'long'), and the sam to > samterm protocol passes pointers around, lopped to 32 bits. Naturally > this causes problems when samterm gets a lopped pointer back and > attempts to use it. > > Unfortunately, I'm not quite sure of the best way to fix this. > Time to go spelunkering the sources. One of the best ways to handle this that I've found is to prototype all of the functions, then find where integers are being passed as pointers, and visa-versa. (ptrs are 64 bits, ints are 32...if you pass `0' where a pointer is expected, it'll be bogus) Then when you compile with an ANSIish compiler (use gcc :) ), it'll tell you about all of the violations. Brendan -- Brendan Kehoe brendan@cygnus.com Cygnus Support, Mountain View, CA +1 415 903 1400 ``In a cruel and imperfect world,'' says critic Rex Reed, ``[Audrey Hepburn] was living proof that God could still create perfection.''