Experimental Physics and
Industrial Control System

Hi Ben,
I'm experiencing a crash when using the sequencer with

pvPut(foo, SYNC)

while it has no access to PV "foo" due to Access Security constraints
(see backtrace.txt).

I can reproduce this with the latest development version of the
sequencer. Replace all pvPuts in the demo example and insert

asSetFilename("does-not-exist.acf")

at the beginning of demo.stcmd to reproduce the problem.

I'm wondering if there is a way to fail a little nicer.

Thanks!

Martin

P.S.: I'm using Base 3.15.6.

-- 
Martin Konrad
Facility for Rare Isotope Beams
Michigan State University
640 South Shaw Lane
East Lansing, MI 48824-1321, USA
Tel. 517-908-7253
Email: [email protected]

#0  0x00007ffff7f147b5 in dbProcessNotify (ppn=0x7fffb00093b8) at ../../../src/ioc/db/dbNotify.c:351
#1  0x00007ffff7f2c411 in dbPutNotifyBlocker::initiatePutNotify (this=0x7fffb00093a0, guard=..., notify=..., dbch=0x7fffb8013100, type=6, count=1, pValue=0x55555562ab68)
    at ../../../src/ioc/db/dbPutNotifyBlocker.cpp:183
#2  0x00007ffff7f28693 in dbContext::initiatePutNotify (this=0x7fffb8000e30, guard=..., chan=..., dbch=0x7fffb8013100, type=6, count=1, pValue=0x55555562ab68, notifyIn=..., 
    pId=0x0) at ../../../src/ioc/db/dbContext.cpp:257
#3  0x00007ffff7f2acc1 in dbChannelIO::write (this=0x7fffb8013448, guard=..., type=6, count=1, pValue=0x55555562ab68, notify=..., pId=0x0)
    at ../../../src/ioc/db/dbChannelIO.cpp:107
#4  0x00007ffff7a6dff6 in ca_array_put_callback (type=6, count=1, pChan=0x7fffb8000fb8, pValue=0x55555562ab68, pfunc=<optimized out>, usrarg=<optimized out>)
    at ../oldChannelNotify.cpp:432
#5  0x00007ffff7603ad2 in pvVarPutCallback (var=0x55555562b888, type=pvTypeDOUBLE, count=1, value=0x55555562ab68, arg=0x7fffb00012e0) at ../pv.c:122
#6  0x00007ffff7e4f4a3 in seq_pvPutTmo (ss=0x55555562ae48, chId=3, compType=SYNC, tmo=10) at ../seq_if.c:515
#7  0x000055555555946c in seqg_action_ramp_1_START (seqg_env=0x55555562ae48, seqg_trn=0, seqg_pnst=0x55555562ae7c) at ../demo.st:102
#8  0x00007ffff7e4cb73 in ss_entry (arg=0x55555562ae48) at ../seq_task.c:361
#9  0x00007ffff7ea8479 in start_routine (arg=0x7fffb804f050) at ../../../src/libCom/osi/os/posix/osdThread.c:403
#10 0x00007ffff7a0f164 in start_thread (arg=<optimized out>) at pthread_create.c:486
#11 0x00007ffff7d35def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Replies:

Re: Sequencer segfaults when using put completion with no access to PV Benjamin Franksen via Tech-talk

Navigate by Date:

Prev: ADPICam driver observations on Linux Jörn Dreyer via Tech-talk

Next: Stream device character parse 吴煊 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  <2019>  2020  2021  2022  2023  2024 

Navigate by Thread:

Prev: ADPICam driver observations on Linux Jörn Dreyer via Tech-talk

Next: Re: Sequencer segfaults when using put completion with no access to PV Benjamin Franksen 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  <2019>  2020  2021  2022  2023  2024