g+
g+ Communities
Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013 
<== Date ==> <== Thread ==>

Subject: asynRecord SEGFAULT?
From: Heinrich du Toit <heinrichdt@tlabs.ac.za>
To: TechTalk EPICS <tech-talk@aps.anl.gov>
Date: Tue, 19 Jun 2007 12:44:09 +0200
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


Replies:
Re: asynRecord SEGFAULT? Eric Norum
RE: asynRecord SEGFAULT? Mark Rivers
Re: asynRecord SEGFAULT? Heinrich du Toit

Navigate by Date:
Prev: support for Pfeiffer RGA? Schuh, Stephen
Next: Re: asynRecord SEGFAULT? Eric Norum
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013 
Navigate by Thread:
Prev: support for Pfeiffer RGA? Schuh, Stephen
Next: Re: asynRecord SEGFAULT? Eric Norum
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013 
ANJ, 10 Nov 2011 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICSv4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·