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 0x00002b2ddd6400c7 in kill () from /lib/libc.so.6 > > (gdb) bt > > #0 0x00002b2ddd6400c7 in kill () from /lib/libc.so.6 > > #1 0x00002b2ddcffd053 in EF_Abort () from /usr/lib/libefence.so.0.0 > > #2 0x00002b2ddcffcc04 in memalign () from /usr/lib/libefence.so.0.0 > > #3 0x00002b2ddcffcc97 in malloc () from /usr/lib/libefence.so.0.0 > > #4 0x00002b2ddcffcd4a in realloc () from /usr/lib/libefence.so.0.0 > > #5 0x00002b2dde0a3ccc in reallocateTable (reference=0x2b2dddfd4f28, size=2, > > count=0) at ./config.y:62 > > Mmm, is the electric fence error message > > ElectricFence Aborting: Allocating 0 bytes, probably a bug.
I tried it again but couldn't find an electric fence error message. I ran BRLTTY under a screen(1) terminal, detached it, then let the display power down. After running BRLTTY again and resuming the screen session, there was no electric fence error message present; BRLTTY had crashed with the same backtrace as quoted above. I would expect any error message to have appeared in the screen(1) session from which BRLTTY was executed. _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://mielke.cc/mailman/listinfo/brltty
