> > Not actually a UTF8 bug. valgrind still screams without any UTF8. > It's something ithreads.
Yeah, it's more like an ithreads bug that gets exposed because the resulting garbage doesn't pass up as valid UTF-8. > Does this give anyone a hunch as to the cause? Double free? Something not properly shared/copied? Wasn't there some special/weird code about GvFILE() in the case of ithreads? -- Jarkko Hietaniemi <[EMAIL PROTECTED]> http://www.iki.fi/jhi/ "There is this special biologist word we use for 'stable'. It is 'dead'." -- Jack Cohen
