From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from highwire.stanford.edu ([171.66.121.166]) by hawkwind.utcs.utoronto.ca with SMTP id <45367>; Wed, 25 Jul 2001 14:16:46 -0500 Received: from highwire.stanford.edu (highwire.stanford.edu [171.66.121.166]) by highwire.stanford.edu (8.10.1/HIGHWIRE2.0) with ESMTP id f6KHOgb05259 for ; Fri, 20 Jul 2001 10:24:42 -0700 (PDT) Message-Id: <200107201724.f6KHOgb05259@highwire.stanford.edu> X-url: http://highwire.stanford.edu/~jimr/ X-face: "!ZH^<"U,NeU:732A To: "sam fans" Dcc: Subject: samterm panic MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <5253.995649882.1@highwire.stanford.edu> Date: Fri, 20 Jul 2001 13:24:42 -0500 Sender: jimr@highwire.stanford.edu 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