From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] sam crashed..
Date: Mon, 28 May 2001 18:39:20 -0400 [thread overview]
Message-ID: <200105282239.SAA04435@augusta.math.psu.edu> (raw)
In-Reply-To: <Pine.LNX.4.30.0105281814010.2438-100000@pali.cps.cmich.edu>
In article <Pine.LNX.4.30.0105281814010.2438-100000@pali.cps.cmich.edu> you write:
>
>I downloaded the idefs patch and wanted to see the contents using sam.
>Sam crahsed. The message is given below.
>
>- ishwar
>----
>term% sam idefs.rc
>sam 204: bad sys call numner 51 pc 114e2
>sam 204: suicide: sys: bad syscall 0x000114e2
>samterm: host read error
>term%
>----
>
Hmm, did you apply a wrap recently and rebuild the kernel but not
rebuild sam? Or vice versa? I've seen sam crash under those
circumstances before.
I doubt it's related to idefs, though. ;-)
- Dan C.
next prev parent reply other threads:[~2001-05-28 22:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-28 22:16 Ish Rattan
2001-05-28 22:39 ` Dan Cross [this message]
2001-05-28 22:16 Russ Cox
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=200105282239.SAA04435@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--cc=9fans@cse.psu.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).