From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] SYSTEM V R1 HELP
Date: Fri, 22 Dec 2017 10:04:56 -0500 [thread overview]
Message-ID: <CAC20D2P-croLXrBtnC+hVtAd2Vcg7qr54QefTy-LMW=Rq5hUHA@mail.gmail.com> (raw)
In-Reply-To: <77B078BE-E3CD-4AFF-93B4-20AF4C8664FD@jctaylor.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]
On Thu, Dec 21, 2017 at 8:51 PM, William Corcoran <wlc at jctaylor.com> wrote:
>
>
> I can’t believe this is a latent defect.
>
Oh I can... SVR1 was not run on 16 bit machines that much I suspect. By
the time SVR1 came on the scene, the VAX and
68K were the primary UNIX systems. AT&T was pushing the 3B but except for
the Telco's not getting much luck.
I'd look at the C runtime library. I bet there is a overflow. IIRC: The
BSD compiler (and Research) compilers used a different buffering scheme
that the Summit folks did - Steve may remember the argument (I only
remember because I ran into that squirmish a few years early when the my
thesis work was causing an strange error in the BSD runtime - I found and
fixed it and mentioned it to Dennis who had the same problem in the V8
compiler at that time).
The point is that 'standard' system in Summit by this time was likely to
been a 3B and Vaxen (i.e. 32 bit) and if there was something that was
assuming a 32 bit int in the runtime and it ran on PDP-11, it could easily
have not been tested.
Clem
ᐧ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171222/0169a536/attachment-0001.html>
next prev parent reply other threads:[~2017-12-22 15:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 22:12 William Corcoran
2017-12-21 22:30 ` Clem Cole
2017-12-22 0:34 ` William Corcoran
2017-12-22 1:51 ` William Corcoran
2017-12-22 1:54 ` William Corcoran
2017-12-22 2:55 ` Random832
2017-12-22 3:47 ` William Corcoran
2017-12-22 9:09 ` Random832
2017-12-22 12:42 ` William Corcoran
2017-12-22 23:48 ` William Corcoran
2017-12-23 0:19 ` Dave Horsfall
2017-12-23 0:21 ` Larry McVoy
2017-12-23 12:26 ` Clem cole
2017-12-22 15:04 ` Clem Cole [this message]
2017-12-22 1:55 ` Random832
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='CAC20D2P-croLXrBtnC+hVtAd2Vcg7qr54QefTy-LMW=Rq5hUHA@mail.gmail.com' \
--to=clemc@ccc.com \
/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).