From: a@9srv.net
To: 9fans@9fans.net
Subject: [9fans] Reliable 9vx(.OSX) crash
Date: Wed, 30 Jul 2008 17:22:58 -0400 [thread overview]
Message-ID: <0e5bb5f8aed495b90516d1c2d3a37ccf@9srv.net> (raw)
Do this:
acme -c1 -f /lib/font/bit/courier/latin1.7.font /lib/kana
Put the mouse in the kana window and scroll down. For me, this
reliably crashes 9vx. Running with -t, I get:
84 acme fault 0 no segment
segment 0xf000000 0x10000000
segment 0x1000 0x42000
segment 0x42000 0x4c000
segment 0x4c000 0x99000
84 acme: unhandled fault va=0 [11000000] eip=3bcdd
cpu0: registers for acme 84
FLAGS=0 TRAP=0 ECODE=0 PC=3BCDD USP=8FF00
AX 00000000 BX 0008FE02 CX 00000052 DX 0008FEB0
SI 00000000 DI 00048646 BP 00000000
56384: signal: sys: abort
This 9vx is post-0.12; I don't have any other systems to try 9vx
on, so I can't say if it shows up elsewhere. A recent drawterm to
an up-to-date (within ~3 days) kills acme with the following:
stringwidth: bad character set for rune 0x0000 in /lib/font/bit/courier/latin1.7.font
stringwidth: bad character set for rune 0x0000 in /lib/font/bit/courier/latin1.7.font
acme: end of string in frcharofpt: '/env/mousescrollsize' file does not exist
acme 39441: suicide: sys: trap: fault read addr=0x0 pc=0x0003bcdd
but drawterm and the cpu server are unharmed. I'm not sure,
but suspect the "/env/mousescrollsize" error is a bug; I think
it's printing the wrong error. Setting mousescrollsize changes
the error to
acme: end of string in frcharofpt: '/lib/font/bit/courier/R.7.1.0' file does not exist
(which is true, although I'm not sure why it's looking for it;
courier/latin1.7.font just says 0x0000 to 0x00FF are in
R.7.1, which does exist).
Within 9vx, something is printed which looks like the same
message from the drawterm'd crash, but goes away before I
can be sure.
Anthony
next reply other threads:[~2008-07-30 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 21:22 a [this message]
2008-07-31 19:24 ` Russ Cox
2008-07-31 23:38 ` Fernan Bolando
2008-08-01 2:50 ` Russ Cox
2008-08-05 16:28 ` Uriel
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=0e5bb5f8aed495b90516d1c2d3a37ccf@9srv.net \
--to=a@9srv.net \
--cc=9fans@9fans.net \
/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).