Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Guido Guenther <guido.guenther@uni-konstanz.de>,
	linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
Subject: Re: SIGIO Handler
Date: Fri, 19 May 2000 14:37:37 +0200	[thread overview]
Message-ID: <20000519143737.C1244@uni-koblenz.de> (raw)
In-Reply-To: <20000518161135.A26055@bert.physik.uni-konstanz.de>; from agx@bert.physik.uni-konstanz.de on Thu, May 18, 2000 at 04:11:36PM +0200

On Thu, May 18, 2000 at 04:11:36PM +0200, Guido Guenther wrote:

> I'm still trying to get the mouse to work under X. The problem seems not
> to be related to X itself but to a kernel/glibc problem. X uses a SIGIO
> handler to "get notified" about mouse events. I wrote my own small SIGIO
> handler(see attached program) which works fine on my intel box but not
> on an indy (glibc-2.0.6-3lm/linux-2.2.13-20000211). Could please someone
> else run the attached program on mips/mipsel and check if it works or
> give me a hint where to start to look for the problem.

Sigh...  Looking at this the first thing I noticed was that the ancient
strace that probably most of us are using prints wrong signal names and
in general seems to have problems.  Maybe I even just found the source of
a good fraction of the GDB problems.  Affects both mips and mips64.
Looking at those ptrace problems first ...

  Ralf

  reply	other threads:[~2000-05-19 14:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-18 14:11 SIGIO Handler Guido Guenther
2000-05-19 12:37 ` Ralf Baechle [this message]
2000-05-22  2:32 ` Hiroyuki Machida
2000-05-22 11:31   ` Ralf Baechle
2000-05-22 13:30     ` Guido Guenther
2000-05-22 19:57       ` Ralf Baechle
2000-05-22 20:07         ` Guido Guenther
2000-05-22 20:13           ` Ralf Baechle
2000-05-24  9:57             ` Guido Guenther
2000-05-23  2:11         ` Ralf Baechle

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=20000519143737.C1244@uni-koblenz.de \
    --to=ralf@oss.sgi.com \
    --cc=guido.guenther@uni-konstanz.de \
    --cc=linux-mips@fnet.fr \
    --cc=linux@cthulhu.engr.sgi.com \
    /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