From: Chris Siebenmann <cks>
To: sam-fans
Subject: Re: sam on DEC OSF/1 Alpha?
Date: Mon, 15 Feb 1993 19:33:44 -0500 [thread overview]
Message-ID: <93Feb15.193359est.2763@hawkwind.utcs.toronto.edu> (raw)
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.
- cks
next reply other threads:[~1993-02-16 0:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-02-16 0:33 Chris Siebenmann [this message]
1993-02-16 1:26 ` brendan
-- strict thread matches above, loose matches on Subject: below --
1993-02-16 3:01 Chris Siebenmann
1993-02-15 16:28 Chris Siebenmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=93Feb15.193359est.2763@hawkwind.utcs.toronto.edu \
--to=sam-fans@hawkwind.utcs.toronto.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).