EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: dbEvent.c line 665
From: "Jeff Hill" <[email protected]>
To: "'Marty Kraimer'" <[email protected]>
Cc: <[email protected]>
Date: Wed, 16 Nov 2005 08:25:44 -0700
> 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 Jeff Hill
References:
Re: dbEvent.c line 665 Marty Kraimer

Navigate by Date:
Prev: Re: dbEvent.c line 665 Marty Kraimer
Next: RE: dbEvent.c line 665 Jeff Hill
Index: 2002  2003  2004  <20052006  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 Marty Kraimer
Next: RE: dbEvent.c line 665 Jeff Hill
Index: 2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Feb 2012 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·