From: wkt@minnie.tuhs.org (Warren Toomey)
Subject: [pups] 2.11BSD "make unix" aborts Error 141
Date: Thu, 20 Mar 2003 07:26:06 +1000 [thread overview]
Message-ID: <20030319212606.GA27436@minnie.tuhs.org> (raw)
In-Reply-To: <200303191759.h2JHx3402619@moe.2bsd.com>
On Wed, Mar 19, 2003 at 09:59:03AM -0800, Steven M. Schultz wrote:
[lamenting a difficult bug in as]
> What might be needed is a decent (or existent ;)) syscall tracing
> capability. That combined with the capability to "coredump a non-0
> exit process) might be enough to track down what's causing 'as'
> to depart the scene prematurely.
This might sound weird, but my Apout user-mode PDP-11 simulator might just
be the tool for this. It would be trivial to put some syscall tracing code
into the simulator, and I have rebuilt a 2.11BSD kernel with Apout several
times.
Warren
next prev parent reply other threads:[~2003-03-19 21:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 17:59 Steven M. Schultz
2003-03-19 21:26 ` Warren Toomey [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-19 18:58 Carl Lowenstein
2003-03-19 17:46 Steven M. Schultz
2003-03-19 16:52 Norman Wilson
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=20030319212606.GA27436@minnie.tuhs.org \
--to=wkt@minnie.tuhs.org \
/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).