devistating speech loss
jason at jasonjgw.net
Sat Dec 31 01:09:34 UTC 2011
<blinux-list at redhat.com> wrote:
>Unfortunately, this doesn't seem to make much sense to me. Is the above
>enough for someone more knowledgeable than I to determine, is
>speech-dispatcher crashing or at-spi? How can I obtain more detailed debug
>file to provide to the appropriate development team?
Both AT-SPI and your Speech-Dispatcher drivers for Festival and Espeak are
crashing with segmentation faults (see the log entries that you posted, and
filter out everything but the segfaults).
Are other processes on your system dying unexpectedly as well? I would suggest
searching the log for other segfault messages.
If there are other segfaults (not related to accessibility), this might be
indicative of hardware problems.
You can obtain debugging information by installing debug symbols for these
packages, if necessary (At-spi and Speech-Dispatcher), then using gdb. You
should be able to set "ulimit -c unlimited" to enable the generation of core
files, then use gdb to investigate the core files. Note that the ulimit
setting has to be changed in the shell that invokes AT-SPI and Orca, directly
I'm sure you can find instructions out there on the Web with a few searches.
You could also try rebuilding AT-SPI and Speech-dispatcher against the latest
libraries, if they were originally compiled with older versions, in case
incompatibilities have arisen and the package dependencies haven't been
More information about the Blinux-list