From: Dawid Toton <dawid.toton@uj.edu.pl>
To: caml-list@yquem.inria.fr
Subject: Corrupt output of printf
Date: Thu, 22 Jan 2009 17:22:20 +0000 [thread overview]
Message-ID: <4978AB4C.7000900@uj.edu.pl> (raw)
I have a program, which output is produced only with Printf.printf .
This inner part is executed by another one (outer) using Unix.system .
The outer executable uses print_endline before and after the inner is run.
From time to time the output of the inner program is corrupt.
Printf.printf seemingly devours parts of single lines, as in these
examples (all lines should have the same structure):
156 In: 5.483000, 1.500000, 1.760000
157 Sb: 5.008000, 1.494000, 1.500000
158 In: 4.498000, 1.494000, 0.750000
159160 Sb: 5.003000, 1.503000, 0.508000
Another one:
138 In: 5.000000, 0.000000, 0.253000
139 In: 5.001000, 1.000140 Sb: 5.500000, 0.000000, 0.000000
141 Sb: 5.500000, 1.000000, 0.000000
This isn't easily reproducible as it happens rarely; subsequent runs are OK.
Could anybody find a possible cause of this behavior?
Dawid
next reply other threads:[~2009-01-22 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 17:22 Dawid Toton [this message]
2009-01-23 11:20 ` [Caml-list] (Not) corrupt " Dawid Toton
2009-01-23 13:16 ` Richard Jones
2009-01-23 14:20 ` Dawid Toton
2009-01-23 15:53 ` Eric Cooper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4978AB4C.7000900@uj.edu.pl \
--to=dawid.toton@uj.edu.pl \
--cc=caml-list@yquem.inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).