Marty Kraimer wrote :
>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.
It turns out that cascaded problems pointed the blame at EPICS sources.
At this moment, I found no evidence against the EPICS source yet after
I tracked down the root cause of the error message. The root cause
has to do with the internal EPICS setup on my computer.
Thanks,
Kate
- Navigate by Date:
- Prev:
Re: "assert (!plink->value.pv_link.pvt)" failed Marty Kraimer
- Next:
Building 3.14.1 for MVME5100 (Internal compiler error) Zoltan Kakucs
- 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:
Re: "assert (!plink->value.pv_link.pvt)" failed Marty Kraimer
- Next:
ca client cannot connect server M.C.Shao
- 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
|