Jason White wrote:
> Patch applied and all is working in initial tests.
I think it's fixed - thanks Samuel.
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@mielke.cc
For general information, go to:
Samuel Thibault wrote:
> I can indeed reproduce it with the XWindow driver. Could you try the
> attached patch?
>
> The fix is making api_unlink restore the brlapi server state to what it
> is on first entering api_link: while the api is unlinked, the driver
> should be not constructed from the
Hello,
Jason White, le Sun 17 Jun 2012 17:40:13 +1000, a écrit :
> Interestingly, this bug was hard to trigger under BRLTTY 4.3, but under 4.4 I
> am finding that I can reliably reproduce it - I just power down the braille
> display, ask another user to log into the machine and start an X session
Jason White (2012/06/17 18:34 +1000):
> The driver code in updateBaumKeys() in the driver which handles this case is:
>
> case BAUM_RSP_PowerdownSignal:
> if (!logBaumPowerdownReason(packet.data.values.powerdownReason)) continue;
> errno = ENODEV;
> return;
I don't know whether this way of
Shérab wrote:
> Hello,
>
> when the device is powered donw, does the driver return
> BRL_CMD_OFFLINE ?
The driver code in updateBaumKeys() in the driver which handles this case is:
case BAUM_RSP_PowerdownSignal:
if (!logBaumPowerdownReason(packet.data.values.powerdownReason)) continue;
errn
Hello,
when the device is powered donw, does the driver return
BRL_CMD_OFFLINE ?
Sherab.
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@mielke.cc
For general information, go to: http://mielke.cc/mailm
Samuel Thibault wrote:
> Could you try this one?
With this patch applied, we still segfault at the same line, with disp ==
NULL.
Interestingly, this bug was hard to trigger under BRLTTY 4.3, but under 4.4 I
am finding that I can reliably reproduce it - I just power down the braille
display, as
Samuel Thibault wrote:
> Could you check what value the disp pointer has here?
It's null when we crashed yesterday (without any patch applied).
$1 = (BrailleDisplay *) 0x0
I'll try your latest patch.
___
This message was sent via the BRLTTY mailing
Jason White, le Sun 17 Jun 2012 11:38:47 +1000, a écrit :
> Samuel Thibault wrote:
>
> > Mmm, indeed, that could happen. Could you test the attached patch?
>
> With the patch applied, we still segfault. Let me know how I can best help.
Could you try this one?
Samuel
Index: Programs/brlapi_se
Jason White, le Fri 15 Jun 2012 13:33:43 +1000, a écrit :
> Program terminated with signal 11, Segmentation fault.
> #0 api_flush (brl=brl@entry=0x7f66f988aa40) at
> ../../Programs/brlapi_server.c:2459
> 2459../../Programs/brlapi_server.c: No such file or directory.
> (gdb) thread apply all b
Samuel Thibault wrote:
> Mmm, indeed, that could happen. Could you test the attached patch?
With the patch applied, we still segfault. Let me know how I can best help.
___
This message was sent via the BRLTTY mailing list.
To post a message, send an
Jason White, le Fri 15 Jun 2012 13:33:43 +1000, a écrit :
> Program terminated with signal 11, Segmentation fault.
> #0 api_flush (brl=brl@entry=0x7f66f988aa40) at
> ../../Programs/brlapi_server.c:2459
Mmm, indeed, that could happen. Could you test the attached patch?
Samuel
Index: Programs/br
Just to keep everybody informed, I've sent Dave the relevant parts of a log,
which would be too large to distribute via the list.
I think we're well on the trail to the ultimate cause of this bug.
I've also sent a patch to the Debian-accessibility list regarding the creation
of packages for debug
Could you post a brltty log file (with -ldebug and -L/path/to/logfile) for when
this occurs as it's unclear what the Baum driver might be doing that could
cause the problem.
--
Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God.
Phone: 1-613-726-0014 | Ottawa, Ontario
Here's a proper backtrace, now that I have installed debugging symbols. I
haven't looked at the code in detail, but we need to avoid dereferencing a
null pointer here (presumably, this code shouldn't be reached if the braille
display is not available).
Core was generated by `/sbin/brltty'.
Program
The circumstances which give rise to this bug appear to be:
1. The braille display is powered down.
2. Someone else logs into the machine and starts an X session. Syslog shows
that the BRLTTY segfault happens within about a minute of the start of the X
session.
3. The X session ends, I switch to
Hello all,
A while ago I reported experiencing occasional, hard to reproduce, segfaults
under BRLTTY 4.3 when my braille display was powered down (it's a Baum
SuperVario 40/Humanware Brailliant).
This time I managed to get a core file.
Unfortunately, Debian does not include a package of debug sy
17 matches
Mail list logo
