9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <9nut@9netics.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Mac drawterm
Date: Fri,  9 Mar 2007 12:32:41 -0800	[thread overview]
Message-ID: <71f2aad81e913ce41d2a4377cb807382@9netics.com> (raw)

here are a couple of bugs just in time for the weekend.

• a deadly bug - happens rarely - when you leave full screen
(apple-F) mode using alt-control, drawterm crashes.  i've included the
interesting part from the crash dump.

Thread 5 Crashed:
0   com.apple.QD                0x91775b2c QDBeginCGContext + 32
1   drawterm                    0x00038364 screenload + 244 (screen.c:703)
2   drawterm                    0x00037db0 flushmemscreen + 140 (screen.c:552)
3   drawterm                    0x00018130 drawflush + 60 (devdraw.c:433)
4   drawterm                    0x0001c508 drawmesg + 8996 (devdraw.c:2006)
5   drawterm                    0x0001a0c8 drawwrite + 656 (devdraw.c:1266)
6   drawterm                    0x0000c8d8 kwrite + 364 (sysfile.c:475)
7   drawterm                    0x0000c9c0 _syspwrite + 80 (sysfile.c:499)
8   drawterm                    0x0000dca4 syspwrite + 100 (sysfile.c:1059)
9   drawterm                    0x00028844 slavewrite + 152 (exportsrv.c:644)
10  drawterm                    0x000283ec blockingslave + 284 (exportsrv.c:501)
11  drawterm                    0x0000b498 tramp + 84 (posix.c:128)
12  libSystem.B.dylib           0x9002b508 _pthread_body + 96


• when a maximized drawterm is hidden (apple-H) and then revived by
clicking on the drawterm icon, it doesn't refresh the screen.
	- i'm guessing the MainWindowEventHandler() needs to handle
	another event?  kEventWindowActivated???



                 reply	other threads:[~2007-03-09 20:32 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=71f2aad81e913ce41d2a4377cb807382@9netics.com \
    --to=9nut@9netics.com \
    --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).