[Octave-bug-tracker] [bug #63930] fprintf problem

[Charles Praplan]

Follow-up Comment #8, bug #63930 (project octave):

I found some systematical behaviour of the problem. This is described below:

Test cases and comparisons are appended (fprintf_bug.tgz). I also join
pictures of the
comparisons because I'm not sure that you see the same thing than me.

1)
If the m-file only writes special characters to the file, the proble does not
appear.

Test case : fprintf_bug4.m => 04.txt

2)
Once a standard character is outputted (incl \n), each 16th character is wrong
(replaced by char 3F).

Test case : fprintf_bug5.m   =>  05.txt


3)
If a second standard character is outputted, the problem disappear for the
rest of the file.

Test case : fprintf_bug6.m   =>  06.txt 

4)
if a third standard character is outputted, the problem appears again for the
rest of the file.

Test case : fprintf_bug7.m   =>  07.txt 


(file #54508)

    _______________________________________________________

Additional Item Attachment:

File name: fprintf_bug.tgz                Size:146 KB
    <https://file.savannah.gnu.org/file/fprintf_bug.tgz?file_id=54508>



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63930>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/