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 > Now I got such a core file, and I'll attach the output of gdb, despite I don't know. which messages you really need. I have an idea of what's going on: Whenever I shut down/reboot my system and let Speakup be activated, e.g. it talks, I get this file. When I deactivate Speakup, and only use braille during shutting/rebooting, there are no such core files. Here's the output: [New Thread 19012] [New Thread 7759] [New Thread 7758] [New Thread 7757] [New Thread 7756] [New Thread 7754] [New Thread 7744] (no debugging symbols found) Core was generated by `espeakup -V de'. Program terminated with signal 11, Segmentation fault. #0 0xb7fac264 in ?? () (gdb) bt #0 0xb7fac264 in ?? () I hope this helps. Hermann
