Here are the valgrind test results with Samuel's syscall patch applied to
Valgrind, and the latest BRLTTY revision with the corrected Baum driver.
I allowed the Brailliant 40 display to power down during this test.
==16074== Memcheck, a memory error detector.
==16074== Copyright (C) 2002-2007, a
On Sat, May 12, 2007 at 02:44:51PM +0200, Samuel Thibault wrote:
> Mmm, would you be able to recompile valgrind? The patch in bug
> http://bugs.kde.org/show_bug.cgi?id=145347
> should fix the ReapUsb warnings.
The patch applied cleanly to valgrind 3.2.3, but with line offsets - evidently
the pat
On Sat, May 12, 2007 at 04:49:38PM +0200, Samuel Thibault wrote:
> > Core was generated by `/bin/brltty -N'.
> > Program terminated with signal 4, Illegal instruction.
> > #0 0x2b2ddd6400c7 in kill () from /lib/libc.so.6
> > (gdb) bt
> > #0 0x2b2ddd6400c7 in kill () from /lib/libc.so.6
>
Great! the cursor routing keys no works in several programs, I've
found. Thanks a lot! But no, the release function doesn't work. So did
Dave not implemented the release patch? in the svn code? I would like
to have it implemented...
Thanks
Lars
___
This
Hi,
Lars Bjørndal, le Sat 12 May 2007 20:23:19 +0200, a écrit :
> I checkd out the latest svn, and tried to patch:
>
> patch -p0 patching file ScreenDrivers/Windows/screen.c
> Hunk #1 FAILED at 322.
> Hunk #2 FAILED at 412.
> 2 out of 2 hunks FAILED -- saving rejects to file
> ScreenDrivers/Wind
Hello, Samuel!
I checkd out the latest svn, and tried to patch:
patch -p0 http://mielke.cc/mailman/listinfo/brltty
Hello Sérgio,
you can either:
edit /etc/default/brltty, or you can type
update-rc.d brltty defaults
to set startup links.
Note: You should choose only one of the two ways.
Hermann
___
This message was sent via the BRLTTY mailing list.
To post a message, s
Hi,
I have ubuntu 7.04 on my desktop and a alva delphi (it is on /dev/ttyS1).
On /etc/init-d, there is a shell script, brltty, to start brltty on system
startup, I think.
I configured /etc/brltty.conf to start on ttyS1 and with al braille display
code, but I think brltty doesn't start (I have to
Hi,
> Core was generated by `/bin/brltty -N'.
> Program terminated with signal 4, Illegal instruction.
> #0 0x2b2ddd6400c7 in kill () from /lib/libc.so.6
> (gdb) bt
> #0 0x2b2ddd6400c7 in kill () from /lib/libc.so.6
> #1 0x2b2ddcffd053 in EF_Abort () from /usr/lib/libefence.so.0.0
>
Mmm, would you be able to recompile valgrind? The patch in bug
http://bugs.kde.org/show_bug.cgi?id=145347
should fix the ReapUsb warnings.
Samuel
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@mielke
Hi,
Jason White, le Sat 12 May 2007 12:48:49 +1000, a écrit :
> Incidentally, from a very quick browse of the latest valgrind output, it
> appears that the warnings about usb_linux.c (lines 275 and 278) are worth
> checking out. If urb isn't guaranteed to be initialized by the ioctl() call
> then
Hi,
Jason White, le Sat 12 May 2007 14:12:58 +1000, a écrit :
> #4 0x2b2ddcffcd4a in realloc () from /usr/lib/libefence.so.0.0
> #5 0x2b2dde0a3ccc in reallocateTable (reference=0x2b2dddfd4f28, size=2,
> count=0) at ./config.y:62
> #6 0x2b2dde0a3ebe in finishCurrentTerminal () a
I tested the fixed Baum braille driver code with my INKA (40 cells + 4 status
cells), and, so far, it's working correctly.
The test with my Brailliant 40 was reported in an earlier message to the list.
___
This message was sent via the BRLTTY mailing li
13 matches
Mail list logo
