another backtrace (was Re: [BRLTTY] Debugging BRLTTY crashes (Baum driver))

[Jason White]

On Fri, May 04, 2007 at 12:11:02AM -0400, Dave Mielke wrote:
> I usually use electric fence.

Electric fence gives interesting results (BRLTTY 3.8-dev, x86_64, core file
generated on startup with electric fence dynamically linked in).

Does this look like a false positive or a potential bug? 

Obviously, we need to get around this before I can debug the crashes that I am
trying to track down.

Reading symbols from /usr/lib/libefence.so.0.0...done.
Loaded symbols for /usr/lib/libefence.so.0.0
Reading symbols from /lib/libdl.so.2...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/libpthread.so.0...done.
Loaded symbols for /lib/libpthread.so.0
Reading symbols from /lib/libc.so.6...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld-linux-x86-64.so.2...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Core was generated by `brltty'.
Program terminated with signal 11, Segmentation fault.
#0  0x00002ac400ff5430 in strcmp () from /lib/libc.so.6
(gdb) bt
#0  0x00002ac400ff5430 in strcmp () from /lib/libc.so.6
#1  0x00002ac400fa6ad4 in setlocale () from /lib/libc.so.6
#2  0x000000000041d7f1 in compileContractionTable (
    fileName=0x2ac401362fe4 "/etc/brltty/en-us-g2.ctb") at ./ctb_compile.c:925
#3  0x000000000040fa45 in loadContractionTable (
    file=0x2ac401360ff0 "en-us-g2.ctb") at ./config.c:462
#4  0x0000000000412e30 in startup (argc=0, argv=0x7fffaa163db0)
    at ./config.c:2146
#5  0x000000000040bb53 in main (argc=1, argv=0x7fffaa163da8) at ./main.c:1101
(gdb) quit