On 05.09.2009 at 22:48:40 William Hubbs <w.d.hubbs at gmail.com> wrote: [...] > The best way for me to fix a core dump would be to have the backtrace > from gdb with the debugging information turned on. To do this, you will > need to add -g to the CFLAGS when you are building espeakup, as follows: > > make CFLAGS="-g" > > Then, the next time you get a core dump, do the following: > > gdb espeakup_executible core_file > bt > quit > > and give me the output from the back trace. > Here is a slightly corrected version, due to a fault by me, the first one seems not what you meant: #0 0xb7ef4264 in ?? () #1 0x08049eb4 in signal_thread () #2 0xb7d254b5 in start_thread () from /lib/i686/cmov/libpthread.so.0 #3 0xb7e19a5e in clone () from /lib/i686/cmov/libc.so.6 And: The thought I had in my last mail seems wrong: Just shut down and restarted my machine with Speakup silent, and the core file was produced anyway. Hermann
