Espeakup sometimes produces core files when shutting down/rebooting

[Hermann]

On 06.09.2009 at 17:47:24 William Hubbs <w.d.hubbs at gmail.com> wrote:

> Hi Hermann,
>
> On Sun, Sep 06, 2009 at 03:53:56PM +0200, Hermann wrote:
>> 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"
>
> Actually I was not quite correct here.  I just found that the command
> needs to be:
>
> make CFLAGS="-ggdb"
>
>> > 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.
>
> Try this again and let me know what the output looks like.
>
I've repeated it, but the output does not change:

#0  0xb7ecc264 in ?? ()
#1  0x08049eb4 in signal_thread ()
#2  0xb7cfd4b5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#3  0xb7df1a5e in clone () from /lib/i686/cmov/libc.so.6

What's the meaning of that lines?
Hermann