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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Trying to use elauncher: _main_ thread failed |
From: | "Crisp, Daniel via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "Hu, Yong" <yhu at bnl.gov>, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>, "anj at anl.gov" <anj at anl.gov> |
Cc: | "Barofsky, Daniel" <barofsky at nscl.msu.edu> |
Date: | Tue, 7 Dec 2021 19:13:16 +0000 |
Ah, I hadn't realized it was davidsaver who'd made this one too. I knew he'd developed pydevsup, which I use elsewhere.
So I did declare the bo correctly, but realized I was still getting the error even when I removed my .db file with the launcher bo. It was as if it was looking for @python ... or info(cmd, "...") for all my non-launcher bo's too. Turns out it was the order in which I added lines to my src/Makefile that was the issue. <myioc>_DBD+= had to be grouped with similar lines. It now seems to be working.
Thank you for the link Yong! I couldn't find anything when I searched for more information.
That program was developed by Michael Davidsaver at NSLS-2 many years ago. How do you load you *.db file in your st.cmd? You need a ‘bo’ record similar to this:
https://github.com/NSLS-II/elauncher/blob/main/elauncherApp/Db/elauncher.db
Yong
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Reply-To: "Crisp, Daniel" <CrispD at nscl.msu.edu>
Date: Monday, December 6, 2021 at 4:04 PM
To: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Cc: "Barofsky, Daniel" <barofsky at nscl.msu.edu>
Subject: Trying to use elauncher: _main_ thread failed
I don't see much documentation about what we call 'elauncher' here, so I'm thinking it might be something site specific? In any case, It's what we use to add PVs that trigger python scripts to our IOCs. I've attached
the source code we add to our src/ folder. We also have an elaunchSupport.dbd file that simply contains two lines 'device(bo, INST_IO, devLauncher, "Launcher")'' and 'variable(launcherVerbose, int)'.
I'm getting an error when attempting to start the IOC, and I'm wondering if someone here could enlighten me as to the problem:
```
A call to 'assert(prec->out.type == INST_IO)' by thread '_main_' failed in ../launcher.c line 80.
Dumping a stack trace of thread '_main_':
[ 0x7f95a3285283]: /lib/x86_64-linux-gnu/libCom.so.3.15.8(epicsStackTrace+0x73)
[ 0x7f95a327e7af]: /lib/x86_64-linux-gnu/libCom.so.3.15.8(epicsAssert+0x4f)
[ 0x5604d5f29b2f]: ../../bin/linux-x86_64/hlc_s800(add_record+0x4f)
[ 0x7f95a3309ea7]: /lib/x86_64-linux-gnu/libdbCore.so.3.15.8(coreRelease+0x837)
[ 0x7f95a330a10a]: /lib/x86_64-linux-gnu/libdbCore.so.3.15.8(iocBuild+0x1a)
[ 0x7f95a330a299]: /lib/x86_64-linux-gnu/libdbCore.so.3.15.8(iocInit+0x9)
[ 0x7f95a32700fb]: /lib/x86_64-linux-gnu/libCom.so.3.15.8(gphDump+0x125b)
[ 0x5604d5f1fea2]: ../../bin/linux-x86_64/hlc_s800(main+0x12)
[ 0x7f95a309e09b]: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)
[ 0x5604d5f1fefa]: ../../bin/linux-x86_64/hlc_s800(_start+0x2a)
EPICS Release EPICS R3.15.8-2+0~20201111173402.6+debian10~1.gbp133abb.
Local time is 2021-12-04 14:33:29.880008830 EST
Please E-mail this message to the author or to tech-talk at aps.anl.govCalling epicsThreadSuspendSelf()
```