Experimental Physics and Industrial Control System
Hi- I'm trying to debug a soft IOC on a couple of solaris machines;
on one of the machines the IOC runs OK, but on the other it starts up
TWO copies of each sequence:
# fbckFugu -- feedback function GUI
seq( &fbckFugu,"STN=HB40,P=X,RING=HER,R=H,name=fbckFuguHX" )
@(#)SEQ Version 2.0.8: Tue Aug 17 15:26:19 PDT 2004
Spawning state program "fbckFugu", thread 4238b0: "fbckFuguHX"
...
epics> seqShow
Program Name Thread ID Thread Name SS Name
fbckFugu 420b28 fbckFuguHX fugu
fbckFugu 4238b0 fbckFuguHX fugu
I can tell they're both running because of debugging output, but you can
see that "seq" only reports starting the second one (thread 4238b0). On
the other solaris machine (same code, same OS... different libs?) it only
starts up one copy.
I've never seen this behaviour before. Any ideas what might cause it?
Something funny in a thread library (wouldn't that cause a lot more
problems)?? ...?
mystified,
Mike
- Navigate by Date:
- Prev:
NCNR DAQ Position Pete Jemian
- Next:
RE: duplicate seq? Laznovsky, Michael
- 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
- Navigate by Thread:
- Prev:
NCNR DAQ Position Pete Jemian
- Next:
RE: duplicate seq? Laznovsky, Michael
- 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