The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: norman@nose.cs.utoronto.ca (Norman Wilson)
Subject: [pups] 2.11BSD "make unix" aborts Error 141
Date: Wed, 19 Mar 2003 11:52:24 -0500	[thread overview]
Message-ID: <200303191652.h2JGqqVJ025026@minnie.tuhs.org> (raw)

Steven M. Schultz:

	It's the exit status of the assembler.   On _some_ modules, the 
	assembler ('as') jumps off into the weeds and executes an 'exit'
	system call with a non-zero value in R0.   141 is a lower case 'a'
	as I recall.

0141 (octal) is 'a.  141 decimal is 0215 octal, i.e. carriage return with
parity.

What seems more likely is that 141 decimal is 0200 + 13 decimal.  If a
simple value returned by wait, that means SIGPIPE + core image, which
seems unlikely.  If an exit status as displayed by the shell, it just
means SIGPIPE (128 + signal number).  Or is signal 13 different in 2.11
than in V7?  (That seems even less likely.)

SIGPIPE doesn't seem entirely unreasonable as an accident that could
happen if something goes wrong in the assembly-language-code-tweaking
part of the kernel build.

Of course if it's a random value handed to sys exit, all rules are off.

Norman Wilson
Toronto ON



             reply	other threads:[~2003-03-19 16:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-19 16:52 Norman Wilson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-19 18:58 Carl Lowenstein
2003-03-19 17:59 Steven M. Schultz
2003-03-19 21:26 ` Warren Toomey
2003-03-19 17:46 Steven M. Schultz
2003-03-19 16:29 Steven M. Schultz
2003-03-19 16:38 ` David Evans
2003-03-17 16:38 [pups] 2BSD build problem - unix.o not too big Steven M. Schultz
2003-03-19  2:24 ` [pups] 2.11BSD "make unix" aborts Error 141 Jonathan Engdahl

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=200303191652.h2JGqqVJ025026@minnie.tuhs.org \
    --to=norman@nose.cs.utoronto.ca \
    /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).