On 16 September 2013 07:29, Richard Brady <rnbr...@gmail.com> wrote:
> Ok, some very strange behaviour here. After further debugging with gdb I
> have found that adding a short sleep before the stdout flush resolves the
> issue:
>
> --- sipp.cpp.orig 2013-09-16 07:23:52.000000000 +0100
> +++ sipp.cpp 2013-09-16 07:26:36.000000000 +0100
> @@ -1545,6 +1545,7 @@
> } else {
> printf("Last Error: %s" SIPP_ENDL, errstart);
> }
> + sipp_usleep(100);
> fflush(stdout);
> }
> if (command_mode) {
>
> Would be most grateful if anyone here knows why?
>
> I'm starting to wonder about how the stdout is used and/or the standard
> libraries and OS role played.
>
> Richard
I'm afraid I haven't seen any sort of truncation like that (and don't
have OS X access to test it) - but if that patch fixes it, I'm happy
to apply it.
Best,
Rob
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
