EPICS Controls 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  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Problem with assert in dbLock.c
From: Andrew Johnson <[email protected]>
To: David Dudley <[email protected]>
Cc: [email protected]
Date: Mon, 19 Nov 2007 10:38:09 -0600
Hi David,

Glad that you're still around.

David Dudley wrote:
Now, whenever I start the system, I get the following message, and
things "die" - as I would expect they would-:

â------------------------------------------------------------------------------------
A call to "assert (status==epicsMutexLockOK)" failed in ../dbLock.c line 247.
EPICS Release EPICS R3.14.9 $R3-14-9$ $2007/02/05 16:31:45$.
Current time Mon Nov 19 2007 09:38:29.509300158.
Please E-mail this message to the author or to [email protected]
Calling epicsThreadSuspendSelf()
Thread scan2 (0xbb630880) suspended
â------------------------------------------------------------------------------------

The same software operates without incident on my Linux development
system, so I'm assuming it's something related to support under
NetBSD that's the culprit.  I'll start looking, but can anyone give
me a pointer on where to start?

There are two completely different implementations of the epicsMutex primitives defined in src/libCom/osi/os/posix/osdMutex.c which are selected depending on whether your version of pthreads implements recursive mutexes or not.


Our build system selects the simpler version on both Solaris and Linux (where presumably recursive mutexes are supported), but the more complex one on Darwin. You might want to remove the -D_XOPEN_SOURCE=500 from your configure/os files for NetBSD if you have it defined as this might solve the problem.

I would suggest typing 'make -s runtests' from the top of your build tree and see whether it passes all of the libCom test code â maybe do that first, then change your configure/os area to see if there's any difference...

- Andrew
--
When a distinguished but elderly scientist states that something is
possible, he is almost certainly right.  When he states that something
is impossible, he is very probably wrong.  -- Arthur C. Clarke

Replies:
Re: Problem with assert in dbLock.c David Dudley
References:
Problem with assert in dbLock.c David Dudley

Navigate by Date:
Prev: 2007 EPICS Meeting (Knoxville) Presentations Kay-Uwe Kasemir
Next: building EPICS base on Mac OS X 10.5 (Leopard) Tom Pelaia
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Problem with assert in dbLock.c David Dudley
Next: Re: Problem with assert in dbLock.c David Dudley
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Nov 2011 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·