Would everyone who has experienced this problem please retest it with the latest revision. I believe I've figured it out.
While the SD API doesn't create subprocesses, it does spawn event threads. Those threads had no way to know that the main thread, i.e. brltty, was counting on having exclusive control over whether or not the death of child signal was being blocked or handled so they inbterfered with brltty's ability to know when its cursor routing subprocess had terminated. Since this change has involved some low-level stuff related to cursor routing, please do let me know immediately if you encounter any sort of problem(s) pertaining to that feature. -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | 2011 May 21 is the Day of Judgement. EMail: [EMAIL PROTECTED] | Canada K2A 1H7 | 2011 Oct 21 is the End of the World. http://FamilyRadio.com/ | http://Mielke.cc/bible/ _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://mielke.cc/mailman/listinfo/brltty
