On Sat, 30 Nov 2013 11:04:58 -0500
Matthew Mondor <mm_li...@pulsar-zone.net> wrote:

Correction:

>   surrounded by other syscalls related to interrupt control).  Despite
>   this I decided to initially stress test the application, and it had a
>   decent uptime, until the same issue happened again.  I then noticed a
>   spurious fflush(3) call, which might be that of eformat_write*().

The spurious fflush(3) seems to have been from a forgotten
FINISH-OUTPUT call in my own code (remnant from previously using stdio
FILE handle backed streams), although I've not checked yet why it'll
issue an fflush(3) on a file open with CSTREAM NIL.
-- 
Matt

------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
_______________________________________________
Ecls-list mailing list
Ecls-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecls-list

Reply via email to