Re: ESCape issue with 1.1.3.2

[Stas Sergeev <stssppnn@yahoo.com>]

Hello.

Bart Oldeman wrote:
>> I think this will cause a null
>> pointer dereference later in
> You are right;
I think that the real problem with
this is that as soon as the low mem
is mapped, we are no longer receive
a SIGSEGV on a null dereference, so
such dereferences may be unnumbered
all around the code...

> here's a second fix (including the hitimer stuff for
> various cases, which in turn includes a fix from you
Actually when I have found that
overflow in miscemu.c (which later
turned out to be a miscompilation of
gcc-2.96-RH) I searched and looked
into the keyboard case and even those
lock-up reports came to my mind, but
I considered that code to be safe
(the t_dif might not exceed the
src_tv.tv_usec value).
Even now I don't see how it can
overflow, but well, maybe I am overlooking
some corner cases, let's see if it fixes
the problem...