Experimental Physics and
Industrial Control System

Eric Norum <[email protected]> · Tue, 19 Jun 2007 06:35:55 -0500

Perhaps you have a runaway pointer in your code which is overwriting
some other part of memory and that causes problems later on.

Can you send your entire driver so we can have a look? If it's
lengthy, please send it to me rather than to the entire list.
On Jun 19, 2007, at 5:44 AM, Heinrich du Toit wrote:
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

--
Eric Norum <[email protected]>
Advanced Photon Source
Argonne National Laboratory
(630) 252-4793

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System