Subject: |
Re: [Merge] ~freddie-akeroyd/epics-base:msi_close_file into epics-base:3.15 |
From: |
Freddie Akeroyd via Core-talk <[email protected]> |
To: |
[email protected] |
Date: |
Mon, 15 Jul 2019 22:13:22 -0000 |
Unfortunately the machine I tested on is no longer showing bad behaviour (it was always transient when i had it, but i had a reproducible failures for a while which fclose fixed). So i think fflush would work, but i'm afraid i can't confirm it with an actual test.
With regard to using fopen, if opt_D is specified then outFile is not opened for output but appears to have its name written to stdout, so fclose(outFP) wold then be fclose(stdout) but also abortExit() would do an
unlink(outFile) which didn't feel right, but i wondered if this was the desired behaviour by how it was usually called. The unlink(outFile) on an error is present in the existing code, I pushed and then reverted a test on opt_D as I though I should check if that was intentional with somebody first.
--
https://code.launchpad.net/~freddie-akeroyd/epics-base/+git/epics-base/+merge/369763
Your team EPICS Core Developers is subscribed to branch epics-base:3.15.
- References:
- [Merge] ~freddie-akeroyd/epics-base:msi_close_file into epics-base:3.15 Freddie Akeroyd via Core-talk
- Navigate by Date:
- Prev:
Jenkins build became unstable: epics-pva2pva-linux32 #123 APS Jenkins via Core-talk
- Next:
Re: [Merge] ~freddie-akeroyd/epics-base:msi_close_file into epics-base:3.15 Andrew Johnson via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
<2019>
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: [Merge] ~freddie-akeroyd/epics-base:msi_close_file into epics-base:3.15 Freddie Akeroyd via Core-talk
- Next:
Re: [Merge] ~freddie-akeroyd/epics-base:msi_close_file into epics-base:3.15 Andrew Johnson via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
<2019>
2020
2021
2022
2023
2024
|