speakup-r lockup analysis so far
okash.khawaja at gmail.com
Tue Sep 19 04:21:41 EDT 2017
On Mon, Aug 28, 2017 at 10:23:31AM +0100, Okash Khawaja wrote:
> Hi John,
> So the last patch I sent, only changes behaviour when
> a) the check 'if (get_sentence_buf(vc, 0) == -1)' in read_all_doc is
> true, and
> b) code is running under context of keyboard_notifier_call() function
> From my understanding the above two conditions occur only when speakup-r
> is typed at beginning of an empty line.
> However if this change causes cursor to end up in wrong position when
> control key is hit, then it must be that the above conditions also occur
> due to reasons other than typing speakup-r at an empty line.
> This patch is the same as before, except that it prints to kernel log
> whenever these two conditions are satisfied. Running it on the same
> document and with serial synth will show that it does happen. Then,
> based on the logs I can investigate why it happens.
I've created a new issue for wrong cursor position when control key is
hit while inside speakup-r: https://github.com/bytefire/speakup/issues/6
More information about the Speakup