gnuspeech-contact
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[gnuspeech-contact] minor typo in .../Monet/MSynthesisController.h (fwd)


From: fmiller
Subject: [gnuspeech-contact] minor typo in .../Monet/MSynthesisController.h (fwd)
Date: Sat, 21 Jul 2012 14:10:57 -0600

woops, I meant to send this to the list, not just to Marcelo.

----------Forwarded message ----------
References: <address@hidden>
<address@hidden>
          <address@hidden>
<address@hidden> In-Reply-To: <address@hidden>
From: address@hidden
To: Marcelo Matuda <address@hidden>
Subject: Re: minor typo in .../Monet/MSynthesisController.h
Date: Sat, 21 Jul 2012 14:02:46 -0600
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset="utf-8"
Content-Transfer-Encoding: 7bit Marcelo Matuda writes:

This is not needed.

Thank you.
I tested on Debian (32-bit) testing and unstable, and the segmentation
fault occurs on both.
I used gdb but the backtrace was useless.

Whew! I was starting to blame myself for that segfault.
Was your Ubuntu installation 32-bit?

Yes, I've been using a six-year-old 32-bit Toshiba Satellite (core duo) to play around with stuff I considered dangerous, like FreeBSD and Ubuntu (my other laptop is a macbook and there are firmware issues and reports of corrupted firmware with at least one distribution). I wouldn't want to use Monet for production on that old equipment but it seemed adequate for purposes of self-education.

Probably the bug is not in the XML code, because the command line tool
(GnuSpeechCLI) works (it uses the XML too). Marcelo

Since it looks like the problem is specific to 32-bit systems, that indicates that the source of the problem could be literally anywhere, does it not?... When I run ldd on the executables built under linux, the first thing listed in the output is "linux-gate.so.1 => (0xf774d000)", with no file on disk? I presume this is something built into the kernel...Again, if the problem is specific to 32-bit systems, then the source of the problem could be literally anywhere, right? I reinstalled debian (stable) on my macbook last night, 64-bit this time. I like stable.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]