9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: nemo@gsyc.escet.urjc.es
To: 9fans@cse.psu.edu
Subject: [9fans] suffering the same crash in acme
Date: Mon, 30 Oct 2000 13:30:23 +0000	[thread overview]
Message-ID: <20001030114016.C4B9F199CC@mail> (raw)

Hi,

[ if this should be posted to 9throuble, let me know and ignore
this message. Sorry if that is the case. ]

My acme is dying often arguing that file `endofframe' does not
exist. That may have to do with the fact that acme fails to paint
a rectangle which looks like the last row of characters for the my
column. But perhaps the rectangle unpainted has to do with not
having enough pixels to fill up one more row of text. I don't know.

The stack trace is attached. I haven't found the exact sequence of
actions that cause acme to abort. If I can gather any other useful
data to get this fixed, let me know.

By the way, rio seems to be kept in bad condition after the acme abort.
If I try to delete the window formerly running acme, the system crashes.
[Didn't record the exact diagnostic, but will do in the next crash].

regards


acme: endofframe: file does not exist
acme 174: suicide: sys: trap: fault read addr=0x0 pc=0x00037303

$c
abort() /sys/src/libc/9sys/abort.c:6 called from error+0x3c /sys/src/cmd/acme/util.c:56
error(s=0x443e2) /sys/src/cmd/acme/util.c:51 called from derror+0xf /sys/src/cmd/acme/acme.c:54
derror(errorstr=0x443e2) /sys/src/cmd/acme/acme.c:52 called from drawerror+0x1f /sys/src/libdraw/init.c:396
drawerror(d=0x92f78, s=0x443e2) /sys/src/libdraw/init.c:387 called from chopframe+0x52 /sys/src/libframe/frinsert.c:85
chopframe(f=0xa41ec, bn=0x0, pt=0x236, p=0x67) /sys/src/libframe/frinsert.c:79 called from frinsert+0x83e /sys/src/libframe/frinsert.c:185
frinsert(p0=0x0, f=0xa41ec, sp=0xb7038, ep=0xb7120) /sys/src/libframe/frinsert.c:99 called from textinsert+0x22a /sys/src/cmd/acme/text.c:366
textinsert(q0=0x0, n=0x74, t=0xa41e8, tofile=0x1, r=0xb7038) /sys/src/cmd/acme/text.c:332 called from xfidwrite+0x8dd /sys/src/cmd/acme/xfid.c:477
xfidwrite(x=0xa49d8) /sys/src/cmd/acme/xfid.c:374 called from xfidctl+0x35 /sys/src/cmd/acme/xfid.c:52
xfidctl(arg=0xa49d8) /sys/src/cmd/acme/xfid.c:42 called from launcher+0x3a /sys/src/libthread/thread.c:898
launcher(arg=0xa49d8, f=0x1e88a) /sys/src/libthread/thread.c:886 called from etext+0x104c8b3




                 reply	other threads:[~2000-10-30 13:30 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=20001030114016.C4B9F199CC@mail \
    --to=nemo@gsyc.escet.urjc.es \
    --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).