Re: Gnopernicus problems
- From: Michael Meeks <michael ximian com>
- To: "Nolan J. Darilek" <nolan_d bigfoot com>
- Cc: gnome-accessibility-list gnome org
- Subject: Re: Gnopernicus problems
- Date: 24 Feb 2003 11:38:51 +0000
Hi Nolan,
On Fri, 2003-02-21 at 16:47, Nolan J. Darilek wrote:
> **MESSAGE**
> speech initialization failed
>
> ** ERROR **: Can't encode unknown type -1073746568
That's almost certainly memory corruption and/or bad error handling.
It's prolly quite hard to pin down since gnopernicus is undergoing lots
of development.
> How do I go about debugging this? How can I determine why speech
> initialization is failing? I've never needed to debug a graphical app
> before; is it somehow possible to get more detailed information
> without needing to read the contents of the error window which
> appears?
You need to attach gdb to gnopernicus, and/or the 'srcore' process that
it spawns. I imagine we need to add a write barrier to srcore, so it's
debuggable:
/* global */
volatile int srcore_barrier = 1;
if (g_getenv ("SRCORE_BARRIER")) {
while (srcore_barrier);
}
And then we can attach the debugger to it easily enough, tweak the
barrier variable to 0 ( p srcore_barrier = 0, continue ), and debug
srcore nicely [ should be in the default CVS gnopernicus IMHO ].
HTH,
Michael.
--
mmeeks gnu org <><, Pseudo Engineer, itinerant idiot
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]