[espeak-ng:master] reported: Memory Access Fixes #github
email@example.com Integration <espeak-ng@...>
Done. Sorry, I totally didn't realize there were tests now. Unfortunately, I see that my changes to readclause.c broke translate.test, and I am not quite sure why.
BTW, when using the command-line binary, sometimes the binary crashes or doesn't crash depending on the source of the input. Malformed text in "speak" tags won't crash espeak if the input is in a file and -f is used, but espeak will crash when the text is supplied on the command line. Here's a transcript that may make things clearer: https://the-brannons.com/pastefiles/espeak-ssml-typescript.txt
I have also found an out-of-bounds read when input starts with two angle
brackets, such as
That one affects both espeak-ng from master and espeak-ng with my readclause.c changes.