RE: A call to 'assert(dbLockIsInitialized)'

[Mark Rivers <rivers@cars.uchicago.edu>]

Did you put that dbpf line before or after iocInit?  It must come after iocInit.

Mark

________________________________________
From: tech-talk-bounces@aps.anl.gov [tech-talk-bounces@aps.anl.gov] on behalf of Heinz Junkes [junkes@fhi-berlin.mpg.de]
Sent: Wednesday, November 25, 2015 2:12 AM
To: EPICS Tech-Talk
Subject: A call to 'assert(dbLockIsInitialized)'

still working with areadetector and EPICS R3.15.3-rc1 today I add the following line to the st.cmd file:

dbpf("DIAS:image1:EnableCallbacks","Enable")


These leads to the following output:


A call to 'assert(dbLockIsInitialized)'
    by thread '_main_' failed in ../../../src/ioc/db/dbLock.c line 246.
Dumping a stack trace of thread '_main_':
[          0x6b3a7b]: ../../bin/linux-x86_64/diasApp(epicsStackTrace+0x4b)
[          0x6ae8ca]: ../../bin/linux-x86_64/diasApp(epicsAssert+0x4a)
[          0x62af72]: ../../bin/linux-x86_64/diasApp(dbScanLock+0x1f2)
[          0x62db9f]: ../../bin/linux-x86_64/diasApp(dbPutField+0x7f)
[          0x640710]: ../../bin/linux-x86_64/diasApp(dbpf+0x60)
[          0x6a2460]: ../../bin/linux-x86_64/diasApp(iocshBody+0xae0)
[          0x48f0d2]: ../../bin/linux-x86_64/diasApp(main+0x12)
[    0x7fd1cea15ec5]: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)
[          0x48f7c2]: ../../bin/linux-x86_64/diasApp(_start+0x29)
EPICS Release EPICS R3.15.3-rc1 $Date: Mon 2015-10-26 17:22:37 +0100$.
Local time is 2015-11-25 09:05:36.884405282 CET
Please E-mail this message to the author or to tech-talk@aps.anl.gov
Calling epicsThreadSuspendSelf()


Cheers,
Heinz