Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017 
<== Date ==> <== Thread ==>

Subject: RE: About: timeout handler of epicsTimer
From: "Jun-ichi Odagiri" <jun-ichi.odagiri@kek.jp>
To: "'Mark Rivers'" <rivers@cars.uchicago.edu>, "'Andrew Johnson'" <anj@aps.anl.gov>
Cc: "'EPICS tech-talk'" <tech-talk@aps.anl.gov>
Date: Mon, 16 Jan 2006 08:40:07 +0900
Dear Mark;

>I don't think I agree with the statement that printf() should not block
>for any significant period of time.
>
>On vxWorks printf() does block, and since the I/O is often going to a
>9600 baud console port, it can be very slow.  In fact if the user types
>^S to pause the output the task will hang until ^Q is typed.

Thank you very much for letting me know on this.
I'll use epicsPrintf() instead of printf() in my timer handler.

Jun-ichi


References:
RE: About: timeout handler of epicsTimer Mark Rivers

Navigate by Date:
Prev: Re: vxStats Kay-Uwe Kasemir
Next: Re: vxstats for Epics 3.13.8 Andrew Johnson
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017 
Navigate by Thread:
Prev: RE: About: timeout handler of epicsTimer Mark Rivers
Next: Re: vxStats Marty Kraimer
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·