Upcall handler

John Tytgat John.Tytgat at aaug.net
Mon Dec 17 13:54:39 PST 2001

In message <f82f48ea4a.Justin at gerph.movspclr.co.uk>
          Justin Fletcher <justin.fletcher at ntlworld.com> wrote:

> [...]
> However, these last three suggestions are more in the area of crash
> prevention, rather than required environment handling (into which UpCall
> most definately falls).

Can't the Wimp claim the ChangeEnvironmentV vector and when it sees the
UpCall handler (or any other offending handler which might be called by
background tasks) being defined in its current swapped in task, replace
the handler by a routine of its own which does some filtering before
calling the original handler ?

John Tytgat, in his comfy chair at home                                 BASS
John.Tytgat at aaug.net                             ARM powered, RISC OS driven

More information about the gcc mailing list