[BRLTTY] BRLTTY 4.4 segfault with backtrace

[Shérab]

Jason White (2012/06/17 18:34 +1000):
> The driver code in updateBaumKeys() in the driver which handles this case is:
> 
> case BAUM_RSP_PowerdownSignal:
>   if (!logBaumPowerdownReason(packet.data.values.powerdownReason)) continue;
>   errno = ENODEV;
>   return;

I don't know whether this way of handling the situation is correct ro
not. I assume this leads to a driver restart but I'm wondering whether
this is really necessary and whether it wouldn't be enough to just
return BRL_CMD_OFFLINE and then when the device is powered up again just
start to return commands again.

That being said, no matter how the driver behaves, the fact that brltty
segfault is, I think, a problem that needs to be addressed anyway.

Sherab.