[BRLTTY] A bug in release 3.10

Jean-Philippe MENGUAL mengualjeanphi at free.fr
Wed Aug 13 20:44:17 EDT 2008


Hi,

I did all the following:

First, Dave, for the moment I only test 3.a0 release. I'll try svn when
the bug on 3.10 is identified and a fix is tried. On the 3.10, I did
autogen, make distclean. Then configkre. Then I installed.

Here's what sans gdb.

Run displays:
[....] # some exit 0, so everything is good, until
rltty: checking braille device: serial:/dev/ttyS0
brltty: [New Thread 0x40cbb950 (LWP 23470)]
checking for braille driver: eu
brltty: opening local socket lock error 13: Permission non accordée.
brltty: Error while initializing socket 0
[Thread 0x40cbb950 (LWP 23470) exited]
[New Thread 0x411b9950 (LWP 23471)]
brltty: initializing braille driver: eu -> serial:/dev/ttyS0
brltty: Detecting param
brltty: serial device opened: /dev/ttyS0: fd=7
brltty: eu: Starting auto-detection process...
brltty: eu: Esysiris detection failed.
brltty: serial device opened: /dev/ttyS0: fd=7
brltty: eu Clio hardware reset requested
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7faec56196e0 (LWP 23467)]
0x000000000042cd28 in clio_readPacket (brl=0x64c4c0, packet=0x64ac00,
size=1024) at eu_clio.c:493
493       if ((needsEscape[((unsigned)buffer[end - 1])] != 1



Then, backtrace says:


#0  0x000000000042cd28 in clio_readPacket (brl=0x64c4c0,
packet=0x64ac00, size=1024) at eu_clio.c:493
#1  0x000000000042d214 in clio_readKey (brl=0x64c4c0) at
eu_clio.c:352
#2  0x000000000042d7a8 in clio_readCommand (brl=0x1,
ctx=BRL_CTX_HELP) at eu_clio.c:373
#3  0x000000000042d82e in clio_init (brl=0x64c4c0, io=<value
optimized out>) at eu_clio.c:320
#4  0x000000000042bca6 in brl_construct (brl=0x64c4c0,
parameters=0x1e223e0, device=0x1e22347 "/dev/ttyS0") at eu_braille.c:168
#5  0x0000000000415839 in constructBrailleDriver () at
./config.c:1616
#6  0x0000000000415b40 in initializeBrailleDriver
(code=0x43d957 "eu", verify=0) at ./config.c:1652
#7  0x0000000000414a73 in activateDriver
(data=0x7fff2e02ffe0, verify=0) at ./config.c:1585
#8  0x0000000000414f6e in activateBrailleDriver
(verify=0) at ./config.c:1776
#9  0x0000000000417c1f in tryBrailleDriver () at
./config.c:1820
#10 0x0000000000418534 in startup (argc=0,
argv=0x7fff2e030450) at ./config.c:2552
#11 0x0000000000412706 in main (argc=5,
argv=0x7fff2e030428) at ./brltty.c:1153

That's all. These messages make me... perplex :D If I can understand a
bit where's the problem with "run" output, "backtrace" lets me.... lol

Well I stay tester and you developpers. :D Yo'll be more able than I to
understand what happens I think.

Sincerely, JP



More information about the BRLTTY mailing list