Experimental Physics and
Industrial Control System

So far, unable to reproduce with an example app created by makeBaseApp and a

debug build. When I type exit it exits w/o crashing.

Do I need to turn on priority based schedualing of libCom/osi threads on
posix?

~/epicsR3.14/epics/appl/iocBoot/iocex$ cat /proc/version
Linux version 2.4.21-20.ELsmp ([email protected]) (gcc
version 3.2.3 20030502 (Red Hat Linux 3.2.3-42)) #1 SMP Wed Aug 18 20:46:40
EDT 2004

> -----Original Message-----
> From: Jeff Hill [mailto:[email protected]] 
> Sent: Wednesday, November 16, 2005 8:26 AM
> To: 'Marty Kraimer'
> Cc: [email protected]
> Subject: RE: dbEvent.c line 665
> 
> 
> 
> > What to do?
> 
> I will pursue it in the debugger.
> 
> Jeff
> 
> > -----Original Message-----
> > From: Marty Kraimer [mailto:[email protected]]
> > Sent: Wednesday, November 16, 2005 8:08 AM
> > To: Jeff Hill
> > Cc: [email protected]
> > Subject: Re: dbEvent.c line 665
> > 
> > 
> > Jeff,
> > 
> > I think we have a big problem.
> > I think this is happening because dbCaTask has called
> > ca_context_destroy.
> > 
> > At the end of dbCaTask I have
> > 
> > printf("before ca_context_destroy\n");
> >     ca_context_destroy();
> > printf("after ca_context_destroy\n");
> >     epicsEventSignal(exitEvent);
> > }
> > 
> > and I get
> > 
> > epics> exit
> > before ca_context_destroy
> > after ca_context_destroy
> > 
> > 
> > 
> > A call to "assert
> > ((epicsMutexLock(((ev_que)->writelock))==epicsMutexLockOK))" 
> > failed in 
> > ../dbEvent.c line 665.
> > EPICS Release EPICS R3.14.7 $$Name: R3-14-2_branch $$ $$Date: 
> > 2004/12/06 
> > 22:31:52 $$.
> > Current time Wed Nov 16 2005 09:00:02.474391200.
> > Please E-mail this message to the author or to 
> > [email protected] Calling epicsThreadSuspendSelf()
> > 
> > If I take out the call to ca_context_destroy(); then exit terminates
> > without error.
> > 
> > What to do?
> > 
> > Marty
> > 
> > Marty Kraimer wrote:
> > 
> > > Andrew Johnson wrote:
> > >
> > >> I just did a CVS update and rebuild on linux-x86, created
> > an example
> > >> app and ran it, which ran fine.  However on pressing
> > Ctrl-D to exit,
> > >> I got this:
> > >>
> > >> epics>
> > >>
> > >>
> > >> A call to "assert
> > >> 
> > ((epicsMutexLock(((ev_que)->writelock))==epicsMutexLockOK))" failed
> > >> in ../dbEvent.c line 665.
> > >> EPICS Release EPICS R3.14.7 $$Name: R3-14-2_branch $$ $$Date:
> > >> 2004/12/06 22:31:52 $$.
> > >> Current time Tue Nov 15 2005 16:20:33.533218000.
> > >> Please E-mail this message to the author or to 
> > [email protected]
> > >> Calling epicsThreadSuspendSelf() 
> > >> filename="../../../src/libCom/taskwd/taskwd.c" line 
> number=174 task 
> > >> 0x80985b8 suspendedapsajnt%
> > >
> > >
> > >
> > >
> > > I am looking into it.
> > >
> > > Marty
> > 
> > 
> 

Replies:

RE: dbEvent.c line 665 Jeff Hill

Re: dbEvent.c line 665 Marty Kraimer

References:

RE: dbEvent.c line 665 Jeff Hill

Navigate by Date:

Prev: Build system problem (was: mrkSoftTest doesn't compile) Ralph Lange

Next: Re: [Fwd: R3.14.8 testing: epicsMessageQueueTestHost fails on linux-x86] Ralph Lange

Index: 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: dbEvent.c line 665 Andrew Johnson

Next: RE: dbEvent.c line 665 Jeff Hill

Index: 2002  2003  2004  <2005>  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024