[BRLTTY] How does a BrlAPI client detect that brltty has quit?

[Willie Walker]

I would definitely expect an exception to be raised, but it's not 
happening. :-(  Something seems to be going awry deeper in the call to 
readKey.  Attached is a new foo.py that eliminates the pyatpi 
references.  The same test procedure applies:

1) Run brltty in one terminal
2) Run foo.py in another
3) Kill brltty
4) foo.py seg faults

I'm not sure how to debug this.

Will

Samuel Thibault wrote:
> Sébastien Hinderer, le Thu 09 Jul 2009 01:47:40 +0200, a écrit :
>> brlapi_readKey will return -1 and the brlapi_errno variable will contain
>> BRLAPI_ERROR_EOF, I think.
> 
> Yes.
> 
>> Not sure how this works in Python,
> 
> That should be translated into the corresponding OperationError being
> raised.
> 
> Samuel
> _______________________________________________
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY at mielke.cc
> For general information, go to: http://mielke.cc/mailman/listinfo/brltty

-------------- next part --------------
A non-text attachment was scrubbed...
Name: foo.py
Type: text/x-python
Size: 1279 bytes
Desc: not available
Url : http://mielke.cc/pipermail/brltty/attachments/20090708/02c3ac16/attachment.py