Re: asynRecord SEGFAULT?

[Heinrich du Toit <heinrichdt@tlabs.ac.za>]

figured it out!!

The order of command in my st.cmd was wrong.

For some reason I must load asynRecord:
dbLoadRecords("../../db/asynRecord.db","P=asyn,R=A,PORT=port0,ADDR=6,IMAX=0,OMAX=0")

before I call iocInit()
else the lockSets aren't setup correctly.

I don't really understand why this is so?

sorry for the trouble :)
There is just so much about epics I am yet to understand

-Heinrich


On Tue, 2007-06-19 at 12:44 +0200, 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
>