Before running medm on the asyn record, at the ioc prompt you could do:
dbpr "myAsynRecord",5
That might help find the problem.
Mark
________________________________
From: [email protected] on behalf of Heinrich du Toit
Sent: Tue 6/19/2007 5:44 AM
To: TechTalk EPICS
Subject: asynRecord SEGFAULT?
Hi
I've started experimenting with asyn.
Now I've created the routines for a driver with Common and devInt32
interfaces.
When I connected my own record (ai) 2 this to read it works fine.
Then I tried connecting a asynRecord to this.
It starts up fine.
But when I run medm to see this record the IOC segfaults.
location: base/src/db/dbLock.c line 242 : plockSet =
plockRecord->plockSet
because plockSet = null
and this is because precord->lst = null
And that must be the lockRecord or something.
I don't understand, the stack trace doesn't even run through asyn or my
own code.
I have no idea where to look for the fault :(
-Heinrich
- References:
- asynRecord SEGFAULT? Heinrich du Toit
- Navigate by Date:
- Prev:
Re: asynRecord SEGFAULT? Eric Norum
- Next:
RE: asynRecord SEGFAULT? Heinrich du Toit
- 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: asynRecord SEGFAULT? Eric Norum
- Next:
RE: asynRecord SEGFAULT? Heinrich du Toit
- 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
|