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: 3.14.8: blockingSockTest - assert() fails.
From: "Jeff Hill" <[email protected]>
To: "'Ralph Lange'" <[email protected]>
Cc: "'EPICS Core Talk'" <[email protected]>
Date: Tue, 8 Nov 2005 09:31:10 -0700
Ralph,

This test isnt quite the same as the others as it is documenting differences
between the various OS implementations of sockets and testing how well we
are able to deal with them.

That test was written to document what is required to interrupt a thread
blocking in socket recv() on the various OS. It looks like the code was
presuming that a CA server was running on the local host, and would not work
otherwise. There is also code there to startup a local server. I went ahead
and instantiated that code and committed it. The test should run standalone
now.

Nevertheless...

O strange behavior could result if a CA server is already running on the
local host when the test starts.
O strange behavior could result if the local os does not allow the process
to exit if a thread is stil running when main exists (I didn't see any
problems with this on linux or windows).

Jeff

> -----Original Message-----
> From: Ralph Lange [mailto:[email protected]] 
> Sent: Tuesday, November 08, 2005 4:28 AM
> To: Jeff Hill
> Cc: EPICS Core Talk
> Subject: 3.14.8: blockingSockTest - assert() fails.
> 
> 
> On both my linux and HP-UX systems calling blockingSockTestHost from 
> base yields
> 
> creek: .../base/3-14-X > bin/hpux-parisc/blockingSockTestHost
> 
> 
> 
> A call to "assert (status == 0)" failed in 
> ../blockingSockTest.cpp line 133. EPICS Release EPICS R3.14.7 
> $$Name: R3-14-2_branch $$ $$Date: 2004/12/06 
> 22:31:52 $$.
> Current time Tue Nov 08 2005 12:10:08.347965000.
> Please E-mail this message to the author or to 
> [email protected] Calling epicsThreadSuspendSelf()
> 
> Adding a printf() shows that
> 
> ../blockingSockTest.cpp: client circuit socket connect() error was 
> "Connection refused"
> 
> I'm not sure what this test is about, documentation is sparse.
> 
> Any ideas?
> 
> Ralph
> 
> -- 
> Ralph Lange               [email protected]     Tel: +49 
> 30 6392-2117
> BESSY Controls Group      www.bessy.de             Fax:      
> ...   -4859
> 



Replies:
Re: 3.14.8: blockingSockTest - assert() fails. Ralph Lange
References:
3.14.8: blockingSockTest - assert() fails. Ralph Lange

Navigate by Date:
Prev: Re: R3.14.8 testing: epicsMessageQueueTestHost fails on linux-x86 Ralph Lange
Next: Re: 3.14.8@Linux: OSS priorities problem? Marty Kraimer
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: 3.14.8: blockingSockTest - assert() fails. Ralph Lange
Next: Re: 3.14.8: blockingSockTest - assert() fails. Ralph Lange
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 ·