>>>>> " " == Marty Kraimer <[email protected]> writes:
> What version of epics are you using. I think I remember this
> problem occuring shohtly after epicsPrintf was developed (First
> appeared in 3.12.1). I think it is fixed in 3.12.2. Johnny
> Tang should have access to the latest beta release for
> 3.12.2. Does it happen with this release?
I'm not sure which version of 3.12 I'm using, but I know that it's not 3.12.2.
Nevertheless, my "semTake returned error" problem has been resolved.
Thanks Matt, Bonnie, David, and Johnny for pointing out that it was a problem
with a database that had not been built against the "right" version of
default.dctsdr. The script I had been using to generate the database
was somehow corrupted and I wasfeeding atdb the wrong version of
default.dctsdr.
All is fine now. Thanks,
-Paul
- References:
- Re: epicsPrint: semTake returned error Marty Kraimer
- Navigate by Date:
- Prev:
Re: epicsPrint: semTake returned error Marty Kraimer
- Next:
Solaris 2.x and EPICS and Motif Rozelle Wright
- 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
2026
- Navigate by Thread:
- Prev:
Re: epicsPrint: semTake returned error Marty Kraimer
- Next:
Solaris 2.x and EPICS Gary P. Carr
- 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
2026
|