On 16/09/13 07:29, Richard Brady 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.orig2013-09-16 07:23:52.000000000 +0100
+++ sipp.cpp2013-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) {

Hi Richard,

I've applied this fix as a new branch, terminal_truncation - would you mind building the code from https://github.com/SIPp/sipp/tree/terminal_truncation and seeing if the fix works?

It's not clear from your message whether a single usleep fixed it or whether you needed a usleep before every fflush - I've assumed the former.

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

Reply via email to