Backend dispatch_hook exception handling about nitro HOT 2 OPEN

The reason why i was catched all these different exceptions here was just to have some statistic at the beginning.

I wanted to know if a hook failed because of a KeyError exception (so the hook implementation was faulty), or if libvmi failed to read the memory, or even if the memory access was not consistent (dump test on ObjectAttributes fields).

This self.stats was just to give me some visibility after running Nitro.

My idea here would be to replace that code by a generic exception handler, to catch everything.

try:
    hook(syscall, self)
except Exception as e:
    logging.exception(e)

It's critically important to catch any exception that could be raised while a hook is being processed.
Otherwise we are not ackowledging the kernel and the VM is frozen and has to be killed

from nitro.

Actually we are already catching everything.

I suggest we should remove these specific exception handlers, and just log the exception on the logging output.

from nitro.