[BRLTTY] How to track efficiently a track

[Samuel Thibault]

MENGUAL Jean-Philippe, le dim. 06 déc. 2020 00:18:50 +0100, a ecrit:
> Well actually I managed to generate a first core. See
> https://people.debian.org/~jpmengual/core

This is saying that the brl_writeWindow function of the brltty brlapi braille driver got
its text as the following:

0x6d, 0x0, 0x0, 0x0,
0x73, 0x0 <repeats 19 times>,
0x21, 0x0, 0x0, 0x0,
0x0, 0x0, 0x0, 0x0,
0xf0, 0xeb, 0x6a, 0xa7,
0x20, 0x0, 0x0, 0x0
0x20, 0x0, 0x0, 0x0
0x20, 0x0, 0x0, 0x0
etc.

It seems like the atspi2 driver returned some bogus data, and this is
making the BrlAPI server reject it since it then does not match the
announced number of sent characters and contains non-existing unicode
characters.

I have submitted a fix on

https://github.com/brltty/brltty/pull/287

How do you prefer to test that it fixes things in your case? An updated
brltty 6.1 package in unstable, or an updated brltty 6.2 package in
experimental?

Samuel