| 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: Filtering messages print on the IOC shell console |
| From: | "Konrad, Martin via Tech-talk" <tech-talk at aps.anl.gov> |
| To: | "J. Lewis Muir" <jlmuir at imca-cat.org>, "Johnson, Andrew N." <anj at anl.gov> |
| Cc: | EPICS tech-talk <tech-talk at aps.anl.gov> |
| Date: | Thu, 26 Mar 2020 22:26:24 +0000 |
Hi Lewis, > A problem I often see on VxWorks VME crate IOC consoles is that output > is corrupted. It looks as if two or more threads or processes are > writing to the console at the same time. Does your suggestion about > where you consider it appropriate to use printf and fprintf include this > situation? How can this be avoided? There is only one IOC shell thread. Assuming that IOC shell commands are executed in a synchronous way there is no risk of corrupting messages printed by printf as long as you stick to Andrews rule and use printf only in IOC shell commands. Cheers, Martin -- Martin Konrad Facility for Rare Isotope Beams Michigan State University 640 South Shaw Lane East Lansing, MI 48824-1321, USA Tel. 517-908-7253 Email: konrad at frib.msu.edu