| 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: print from interrupt |
| From: | Eric Norum <[email protected]> |
| To: | "D. Peter Siddons" <[email protected]> |
| Cc: | Mark Rivers <[email protected]>, [email protected] |
| Date: | Fri, 27 Feb 2004 16:22:53 -0600 |
Thanks to all who responded. I should have made it clear that I was talking about an RTEMS app., which only has epicsInterruptContextMessage(), which can only print a string, no formatting. Eric Norum suggested using snprintf() to fill a buffer and pass that to epicsInterruptContextMessage(). That seems to work fine. I had the impression before that calling any of the xprintf() commands from within interrupt context wasn't allowed, but apparently the string variants are OK.The string variants can't ever block so they're safe to call from an interrupt handler -- with one small caveat. Interrupt handlers typically do not have their own floating point context so you've got to ensure that snprintf does not execute any floating-point instructions.
Pete.
-- Eric Norum [email protected] Advanced Photon Source Phone: (630) 252-4793 Argonne National Laboratory