9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: underspecified <underspecified@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] p9p acme freezes on devdraw read in MacOS X
Date: Wed,  8 Oct 2008 20:23:08 +0900	[thread overview]
Message-ID: <ab4cf6420810080423q1eba5b7sb79f421c5cdc8d4@mail.gmail.com> (raw)
In-Reply-To: <20081008083600.GN10037@hermes.my.domain>

[-- Attachment #1: Type: text/plain, Size: 2086 bytes --]

Greetings,
I have been using a scroll wheel in p9p's acme on OS-X for some time without
any problems.
This raises a few questions about your setup:

1) Are you sure you are running the new, native gui version? Your hg info
suggests this is the case, but I want to make sure you recompiled the
binaries between now and then.
2) What kind of mouse is is?
3) Does the scroll wheel behave normally in other apps on OS-X?
4) Are you using any non-standard mouse drivers?
5) If you are on a laptop, does scrolling with the touchpad cause this
error?

--underspecified

On Wed, Oct 8, 2008 at 5:36 PM, Christian Kellermann <
Christian.Kellermann@nefkom.net> wrote:

> Dear List,
>
> I am experiencing a strange behaviour of p9p acme: When I scroll
> with the mouse wheel acme just hangs. The console prints acme: bad
> rpc tag 2 (no one waiting on that tag)
>
> attaching with gdb says:
>
> 0x9526a1b5 in read$UNIX2003 ()
> (gdb) bt
> #0  0x9526a1b5 in read$UNIX2003 ()
> #1  0x000089e7 in threadmain ()
> #2  0x0001aeac in threadmainstart (v=0x0) at thread.c:699
> #3  0x0001a808 in threadstart (y=552960, x=0) at thread.c:95
>
> and detaching makes acme crash completely with
>
> settag/send tag 3: Broken pipe
> settag/send tag 3: Broken pipe
> Oct  8 10:27:23.908 write error: Broken pipe
> settag/send tag 3: Broken pipe
>
> Has any one else seen this? It feels like a race condition since I
> cannot reproduce it reliably other than opening a window with some
> content and scrolling around with the mouse wheel. I have tried to
> pull from the repo but it seems that
>
> changeset:   2915:dd72218f97d9
> tag:         tip
> user:        Russ Cox <rsc@swtch.com>
> date:        Thu Aug 14 10:29:29 2008 -0400
> summary:     rc: fix local variables in functions
>
> is the latest tip.
>
> What can I do to help debugging this? It is really an annoying bug
> I must say.
>
> Thanks for your insights,
>
> Christian
>
> --
> You may use my gpg key for replies:
> pub  1024D/47F79788 2005/02/02 Christian Kellermann (C-Keen)
>

[-- Attachment #2: Type: text/html, Size: 2737 bytes --]

  reply	other threads:[~2008-10-08 11:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-08  8:36 Christian Kellermann
2008-10-08 11:23 ` underspecified [this message]
2008-10-08 11:40   ` Christian Kellermann
2008-10-08 12:09     ` underspecified
2008-10-08 12:20       ` Christian Kellermann
2008-10-08 20:41         ` Russ Cox
2008-10-08 22:05           ` Russ Cox
2008-10-08 22:53             ` Noah Evans
2008-10-09  7:18               ` Philippe Anel
2008-10-08 11:44 erik quanstrom
2008-10-08 12:01 ` underspecified
     [not found] <d3f8019b394810b0dbada3b5e2414f23@quanstro.net>
2008-10-08 11:51 ` Christian Kellermann

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=ab4cf6420810080423q1eba5b7sb79f421c5cdc8d4@mail.gmail.com \
    --to=underspecified@gmail.com \
    --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).