EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
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: "assert (!plink->value.pv_link.pvt)" failed
From: Marty Kraimer <[email protected]>
To: "Feng, Shuchen" <[email protected]>
Cc: "'[email protected]'" <[email protected]>
Date: Fri, 28 Mar 2003 07:21:27 -0600
Feng, Shuchen wrote: 
I am porting a device drvier for the Joerger scaler VSC16
from vxWorks to RTEMS.  The EPICS release is R3.14.0beta2.
The IOC ran the scaler_init routine sucessfully.  However,
it failed somewhere before (? or in ?) the scaler_init_record
routine. The erro message is :

A call to "assert (!plink->value.pv_link.pvt)" failed in ../dbCa.c line 157.
EPICS Release EPICS R3.14.0.beta.2 $R3-14-0-beta-2$ $2002/07/30 21:40:55$.
Current time Wed Mar 26 2003 16:46:05.420000000.
Please E-mail this message to the author or to [email protected]
Calling epicsThreadSuspendSelf()


Here it is. I am reporting this error to the tech-talk. Any clue ?
The problem is that the error did not mention which line of the database
triggered the error.  I was able to load database for a bitIO device
sucessfully with the same platform.


Any pointer would be highly appreciated,
Kate


I am not familiar with the Joerger VSC16 device support so it is hard to know where to start.

The error is because some DBF_XXXLINK has not been initialized properly.

Some suggestions.

If you know how to use a linux source level debugger it will make your task easier.

If not do the following:

Put printf statement in the init_record routines of both record and device support. Put the printf statement at entrace and exit and before/after any call to other routines.

Then send another Email message showing.

1) The output of the printfs
2) The source for the device support.
3) If any recordtype not coming from base is used, it's source.
3) The record definitions from the database that causes the problem.

Marty Kraimer




References:
"assert (!plink->value.pv_link.pvt)" failed Feng, Shuchen
Navigate by Date:
Prev: ca client cannot connect server M.C.Shao
Next: RE: "assert (!plink->value.pv_link.pvt)" failed Feng, Shuchen
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: "assert (!plink->value.pv_link.pvt)" failed Feng, Shuchen
Next: RE: "assert (!plink->value.pv_link.pvt)" failed Feng, Shuchen
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 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·