Date: Sun, 25 Apr 1999 11:59:59 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Alberto Chessa <achessa AT fiar DOT finmeccanica DOT it>
cc: djgpp AT delorie DOT com
Subject: Re: kbhit() and SIGALRM
In-Reply-To: <372048CA.39306E43@fiar.finmeccanica.it>
Message-ID: <Pine.SUN.3.91.990425115936.9117e-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Fri, 23 Apr 1999, Alberto Chessa wrote:

> Has kbhit() problem when interrupted by SIGALRM (generated with
> setitimer(), not with alarm()) ? It seem to hang-on and simple never
> return. It could be a bug of my program or there are known problems on
> kbhit() ?

I'm not aware of any such problems.  If the comments below don't
explain your problem, please post a minimal program that exhibits this
behvior.

> (I know, the signal delivering is delayed during DOS system call. That's
> why I'm using a kbhit() based loop instead of a getch()).

Signals are delayed during *all* real-mode call, including a call to
`kbhit' (which issues a BIOS interrupt).

> p.s.: I can post a detailed problem report if required

That is always a good idea.