Argonne National Laboratory

Experimental Physics and
Industrial Control System

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  <20192020  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  <20192020 
<== Date ==> <== Thread ==>

Subject: A call to 'assert(dbLockIsInitialized)' by thread '_main_'
From: Iain Marcuson via Tech-talk <tech-talk@aps.anl.gov>
To: "tech-talk@aps.anl.gov" <tech-talk@aps.anl.gov>
Date: Thu, 25 Apr 2019 20:14:37 +0000

I am writing a driver for a camera we have developed.  Part of the scheme involves monitoring a PV at about 20 Hz to check for a trigger.  I get this message on trying to read the PV.  I tried an initial read in the main thread to capture the problem before too much else was started.

 

A call to 'assert(dbLockIsInitialized)'

    by thread '_main_' failed in ../../../src/ioc/db/dbLock.c line 246.

Dumping a stack trace of thread '_main_':

[    0x7fcec9b5334b]: /home/iainm/local/opt/epics/base/lib/linux-x86_64/libCom.so.3.15.4(epicsStackTrace+0x4b)

[    0x7fcec9b4c8ca]: /home/iainm/local/opt/epics/base/lib/linux-x86_64/libCom.so.3.15.4(epicsAssert+0x4a)

[    0x7fcec9d9cdb2]: /home/iainm/local/opt/epics/base/lib/linux-x86_64/libdbCore.so.3.15.4(dbScanLock+0x1f2)

[    0x7fcec9d9f45c]: /home/iainm/local/opt/epics/base/lib/linux-x86_64/libdbCore.so.3.15.4(dbGetField+0x2c)

[          0x40dbef]: ../../bin/linux-x86_64/HPE3631Atest(_ZN10SpectroCCDC2EPKcS1_imiiS1_+0x74f)

[          0x40de82]: ../../bin/linux-x86_64/HPE3631Atest(_ZL14configCallFuncPK11iocshArgBuf+0x62)

[    0x7fcec9b3efb0]: /home/iainm/local/opt/epics/base/lib/linux-x86_64/libCom.so.3.15.4(iocshBody+0xae0)

[          0x40c3b2]: ../../bin/linux-x86_64/HPE3631Atest(main+0x12)

[    0x7fcec9249f45]: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)

[          0x40c3fd]: ../../bin/linux-x86_64/HPE3631Atest(_start+0x29)

EPICS Release EPICS R3.15.4 $Date: Fri 2016-05-27 08:54:04 +0200$.

Local time is 2019-04-25 13:01:39.451503845 PDT

Please E-mail this message to the author or to tech-talk@aps.anl.gov

 

The record in question is

 

record(longin, "$(P)$(R)Cmd_GET_HW_TRIG_DR0")

{

}

 

And the reading code is

 

pv_opts = 0;

pv_nreq = 1;

dbGetField(&hw_trigger_addr_, DBR_LONG, &pv_val,

                     &pv_opts, &pv_nreq, NULL);

 

pv_val, pv_opts, and pv_nreq are of type long, as in other parts of the code that work.

 

What might I do or look up to solve this problem?

 

Thank you,

 

Iain.


Replies:
Re: A call to 'assert(dbLockIsInitialized)' by thread '_main_' Michael Davidsaver via Tech-talk

Navigate by Date:
Prev: database or new record for blocking setpoint/readback process control Pearson, Matthew R. via Tech-talk
Next: Re: A call to 'assert(dbLockIsInitialized)' by thread '_main_' Michael Davidsaver via Tech-talk
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  <20192020 
Navigate by Thread:
Prev: Re: database or new record for blocking setpoint/readback process control Pearson, Matthew R. via Tech-talk
Next: Re: A call to 'assert(dbLockIsInitialized)' by thread '_main_' Michael Davidsaver via Tech-talk
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  <20192020 
ANJ, 25 Apr 2019 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·