From: "James A. Robinson" <jim.robinson@stanford.edu>
To: "sam fans" <sam-fans@hawkwind.utcs.toronto.edu>
Subject: samterm panic
Date: Fri, 20 Jul 2001 13:24:42 -0500 [thread overview]
Message-ID: <200107201724.f6KHOgb05259@highwire.stanford.edu> (raw)
Cause some folks expressed an interest in when sam panics, I
was asked to make a note of it to this list. =)
I'm using the new sam with acme data structures, combined with the
old samterm. Every once in a while I get a panic. I never really
payed attention to if it was sam or samterm. =(
I just got a panic from samterm when I:
opened a file locked by RCS
made a change
tried to save
got permission denied
in another window, checked out the file from RCS
tried to save the file again
samterm spat out the following and dumped core
samterm: host mesg: count 24933 114x 101x 97x te "local_env"
...ignored
74 65 20 22 6c 6f 63 61 6c 5f 65 6e 76 22 a 6 2 samterm: host mesg: count 24933 114x 101x 97x te "local_env"
...ignored
74 65 20 22 6c 6f 63 61 6c 5f 65 6e 76 22 a 6 2 samterm: host mesg: count 24933 114x 101x 97x te "local_env"
...ignored
74 65 20 22 6c 6f 63 61 6c 5f 65 6e 76 22 a 6 2 samterm: host mesg: count 24933 114x 101x 97x te "local_env"
...ignored
74 65 20 22 6c 6f 63 61 6c 5f 65 6e 76 22 a 6 2 type 114 count 24933
samterm:panic: count>DATASIZE: Error 0
I can't reproduce the problem. I took the exact same steps
as before, and sam properly warned me that I might be changing
an already altered file, and then let me save.
Jim
reply other threads:[~2001-07-25 19:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200107201724.f6KHOgb05259@highwire.stanford.edu \
--to=jim.robinson@stanford.edu \
--cc=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).