[BRLTTY] compiling new driver

Samuel Thibault samuel.thibault at ens-lyon.org
Fri Mar 22 12:32:24 EDT 2013


ZSIAK Gergo Pal, le Thu 21 Mar 2013 16:33:21 +0100, a écrit :
> * The log file is created, and based on date, it is modified often, but there aren't any messages.

Possibly some buffering in the io primitives, are you flushing your
file?

> * In the windows log there are error messages, like:
> ** freopen[stdin] error 2: No such file or directory.
> ** freopen[stdout] error 2: No such file or directory.
> ** freopen[stderr] error 2: No such file or directory.
> ** CreateNamedPipe error 5: Access denied.
> 
> Do you have any idea?

Without seeing the actual code, it's hard to have any idea :)

> What do you think, which is the best way of testing a new driver?

We usually put debugging messages through the logMessage helper, and get
them from debug.log (see run-debug.bat), and simply try with the real
device.

Samuel


More information about the BRLTTY mailing list