Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017 Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
<== Date ==> <== Thread ==>

Subject: Re: terminate called after throwing an instance of 'epicsMutex::invalidMutex'
From: Marty Kraimer <mrkraimer@comcast.net>
To: Heinz Junkes <junkes@fhi-berlin.mpg.de>, core-talk@aps.anl.gov
Date: Sun, 4 Jun 2017 15:16:28 -0400
On 06/04/2017 01:32 PM, Heinz Junkes wrote:
I replaced pvaClientCPP and pvAccessCPP with the code you provide

Now the tests runs without error:

Good news!!!

I did make some more changes to
https://github.com/mrkraimer/pvAccessCPP/

The changes resulted from suggestions made by Michael Davidsaver.

Marty

make -C O.linux-x86_64 -f ../Makefile TOP=../.. \
    T_A=linux-x86_64 runtests
make[2]: Entering directory '/home/cryvisil/EPICS/V4/exampleCPP/test/O.linux-x86_64'
perl -CSD -MTest::Harness -e 'runtests @ARGV if @ARGV;' pvaClientTest.t pvaClientTestPutData.t pvaClientTestGetData.t pvaClientTestMonitorData.t pvaClientTestPutGetMonitor.t pvaClientTestPutGet.t
pvaClientTest.t ............... 1/7 CA.Client.Exception...............................................
    Warning: "Identical process variable names on multiple servers"
    Context: "Channel: "DBRdouble01", Connecting to: 141.14.133.59:32972, Ignored: 10.20.30.1:32972"
    Source File: ../cac.cpp line 1320
    Current Time: Sun Jun 04 2017 19:30:08.148992503
..................................................................
pvaClientTest.t ............... ok
pvaClientTestPutData.t ........ ok
pvaClientTestGetData.t ........ ok
pvaClientTestMonitorData.t .... ok
pvaClientTestPutGetMonitor.t .. ok
pvaClientTestPutGet.t ......... ok
All tests successful.
Files=6, Tests=119,  6 wallclock secs ( 0.05 usr  0.00 sys +  0.41 cusr  0.06 csys =  0.52 CPU)
Result: PASS
make[2]: Leaving directory '/home/cryvisil/EPICS/V4/exampleCPP/test/O.linux-x86_64'
make[1]: Leaving directory '/home/cryvisil/EPICS/V4/exampleCPP/test’

Heinz


------------------------------------------------------------------------------
Fritz-Haber-Institut    | Phone:         (+49 30) 8413-4270
Heinz Junkes             | Fax (G3+G4):   (+49 30) 8413-5900
Faradayweg 4-6        | 
D - 14195 Berlin        | E-Mail:     junkes@fhi-berlin.mpg.de
------------------------------------------------------------------------------

On 4. June 2017 at 16:50:13, Marty Kraimer (mrkraimer@comcast.net) wrote:

I have also spent some time looking at the  epicsMutex::invalidMutex() messages.

Is it possible to rerun your tests with using a version of pvAccessCPP and pvaClientCPP from my git repository?
Thus
git clone https://github.com/mrkraimer/pvaClientCPP.git

Marty



On 06/04/2017 09:23 AM, Heinz Junkes wrote:
Hi Folks,

today I played with the the epics 3.16 release on linux-86_64 …

I installed epics base from git-hub.
compile, make runtests … ok

Then the v4 stuff also from git:



make runtests in example CPP leads to the follwing error:

...
make[1]: Entering directory '/home/cryvisil/EPICS/V4/exampleCPP/test'
make -C O.linux-x86_64 -f ../Makefile TOP=../.. \
    T_A=linux-x86_64 runtests
make[2]: Entering directory '/home/cryvisil/EPICS/V4/exampleCPP/test/O.linux-x86_64'
perl -CSD -MTest::Harness -e 'runtests @ARGV if @ARGV;' pvaClientTest.t pvaClientTestPutData.t pvaClientTestGetData.t pvaClientTestMonitorData.t pvaClientTestPutGetMonitor.t pvaClientTestPutGet.t
pvaClientTest.t ............... 6/7 terminate called after throwing an instance of 'epicsMutex::invalidMutex'
  what():  epicsMutex::invalidMutex()
pvaClientTest.t ............... Dubious, test returned 134 (wstat 34304, 0x8600)
All 7 subtests passed
pvaClientTestPutData.t ........ 1/38 terminate called after throwing an instance of 'epicsMutex::invalidMutex'
  what():  epicsMutex::invalidMutex()
pvaClientTestPutData.t ........ Dubious, test returned 134 (wstat 34304, 0x8600)
All 38 subtests passed
pvaClientTestGetData.t ........ 1/26 terminate called after throwing an instance of 'epicsMutex::invalidMutex'
  what():  epicsMutex::invalidMutex()
pvaClientTestGetData.t ........ Dubious, test returned 134 (wstat 34304, 0x8600)
All 26 subtests passed
pvaClientTestMonitorData.t .... 1/26 terminate called after throwing an instance of 'epicsMutex::invalidMutex'
  what():  epicsMutex::invalidMutex()
pvaClientTestMonitorData.t .... Dubious, test returned 134 (wstat 34304, 0x8600)
All 26 subtests passed
pvaClientTestPutGetMonitor.t .. 1/19 terminate called after throwing an instance of 'epicsMutex::invalidMutex'
  what():  epicsMutex::invalidMutex()
pvaClientTestPutGetMonitor.t .. Dubious, test returned 134 (wstat 34304, 0x8600)
All 19 subtests passed
pvaClientTestPutGet.t ......... ^C/home/cryvisil/EPICS/base/configure/RULES_BUILD:337: recipe for target 'runtests' failed
make[2]: [runtests] Interrupt (ignored)
/home/cryvisil/EPICS/base/configure/RULES_ARCHS:58: recipe for target 'runtests.linux-x86_64' failed
make[1]: *** [runtests.linux-x86_64] Interrupt
/home/cryvisil/EPICS/base/configure/RULES_DIRS:84: recipe for target 'test.runtests’ failed
...
Test Summary Report
-------------------
pvaClientTest.t             (Wstat: 34304 Tests: 7 Failed: 0)
  Non-zero exit status: 134
pvaClientTestPutData.t      (Wstat: 34304 Tests: 38 Failed: 0)
  Non-zero exit status: 134
pvaClientTestGetData.t      (Wstat: 34304 Tests: 26 Failed: 0)
  Non-zero exit status: 134
pvaClientTestMonitorData.t  (Wstat: 34304 Tests: 26 Failed: 0)
  Non-zero exit status: 134
pvaClientTestPutGetMonitor.t (Wstat: 34304 Tests: 19 Failed: 0)
  Non-zero exit status: 134
pvaClientTestPutGet.t       (Wstat: 34304 Tests: 3 Failed: 0)
  Non-zero exit status: 134
Files=6, Tests=119,  6 wallclock secs ( 0.05 usr  0.00 sys +  0.41 cusr  0.08 csys =  0.54 CPU)
Result: FAIL
Failed 6/6 test programs. 0/119 subtests failed.

Heinz




Replies:
Re: terminate called after throwing an instance of 'epicsMutex::invalidMutex' Michael Davidsaver
References:
terminate called after throwing an instance of 'epicsMutex::invalidMutex' Heinz Junkes
Re: terminate called after throwing an instance of 'epicsMutex::invalidMutex' Marty Kraimer
Re: terminate called after throwing an instance of 'epicsMutex::invalidMutex' Heinz Junkes

Navigate by Date:
Prev: RE: Build problem Mark Rivers
Next: RE: Build problem Mark Rivers
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
Navigate by Thread:
Prev: Re: terminate called after throwing an instance of 'epicsMutex::invalidMutex' Heinz Junkes
Next: Re: terminate called after throwing an instance of 'epicsMutex::invalidMutex' Michael Davidsaver
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
ANJ, 06 Jun 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·