nanogui: Got a doozy of a bug with timer events
Subject:
Re: [nanogui] Got a doozy of a bug with timer events
From:
"Greg Haerr" ####@####.####
Date:
13 Jun 2004 02:25:18 +0100
Message-Id: <0da201c450e5$4fdf8cc0$3aba46a6@xmission.com>
: I don't use stdin, stdout or stderr. Here's what I did as a test though.
The nano-X server may use or depend on those three file descriptors
being in 0, 1, 2 position. that's why I suggested the previous test.
Otherwise, we need to look at the Gd*Timer routines, looking for
something suspicious. As I think of it, the select() call is
used in nanox/srvmain.c to wait for timer events, and it uses
file descriptors that it waits on as well. Those file descriptors
may be in different positions from a task started at boot
and not associated with a terminal. (we're talking nano-X server
here, not your apps)
Regards,
Greg
: I removed the GrCreateTimer, and started a thread that used nanosleep
: and then sent a GrInjectKeyboardEvent when the timeout occured. This
: worked OK. Not a solution I want to use at all though. The app does
: everything else it is supposed to do which involves receiving and
: displaying "real world" information. via it's own execution and via
: pipes from other "spawned" apps.
:
: Just the timer does not work.
:
: tj
:
:
:
: ---------------------------------------------------------------------
: To unsubscribe, e-mail: ####@####.####
: For additional commands, e-mail: ####@####.####
:
:
