In message <eae02b5551...@hobbes.bass-software.com>
John Tytgat <john.tyt...@aaug.net> wrote:
> In message <ede0d35451.mar...@bach.planiverse.com>
> Martin Wuerthner <mar...@mw-software.com> wrote:
>> Then, I tried building with r4398 and it still works, so r4398 was not
>> responsible. Finally, I tried r4458 and even that worked. I double
>> checked with r4459 and it fails. So, this proves that r4459 was
>> responsible for the problem.
> Thanks for spending time figuring this out. The r4459 was indeed the
> culpit but understanding why wasn't so trivial. In turned out that this
> change wrongly called an internal flush call resulting in a failure
> when we were in the (v)s(n)printf() usecase and this resulted in a
> -1 return value. In Ghostscript the return value of vsprintf() was
> used as fwrite(..., stdout) nmemb parameter which made stdout go into
> error mode preventing any further output.
> Fixed with r4786 change.
Great, thank you for fixing this problem.
Martin
--
---------------------------------------------------------------------
Martin Wuerthner MW Software mar...@mw-software.com
---------------------------------------------------------------------
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
