EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  <20012002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  <20012002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: ca assert
From: Vladimir Sirotenko <[email protected]>
To: Jeff Hill <[email protected]>, [email protected]
Date: Wed, 01 Aug 2001 13:44:22 -0500
Hi Jeff,

Thanks, I suspect that that was OS related problems as you indicated. Our CA
client runs on OSF1, v5 machine.
This was first time in about a month continous running we saw this error and
can not reproduce it easily.
So we'll keep eye on it.

Vladimir

----- Original Message -----
From: "Jeff Hill" <[email protected]>
To: "Vladimir Sirotenko" <[email protected]>; <[email protected]>
Sent: Wednesday, August 01, 2001 12:31 PM
Subject: RE: ca assert


>
> Vladimir,
>
> >
> > We are running DAQ application which queries portable CA server running
on
> > NT for several PV's.
> > Everything worked well but today it crashed with the following massage:
> >
> > A call to "assert (status == 0)" failed in ../iocinf.c line 1472.
> > The file "core" will be created in the current working directory.
> > Please save this file and the text of this message in order to assist
> > in diagnosing this problem.
> > Please contact the author of this software or else send the text of
> > this message to "[email protected]"
> > This problem occurred in "@(#)Version R3.13.4 $2000/12/15 15:52:33$"
> >
> > Could someone advise us what may cause this crash?
>
> There appears to be a problem with the following code that closes the
socket
> when disconnecting from a server.
>
>   status = socket_close (piiu->sock_chan);
> assert (status == 0);
>
> What OS was this _client_ running on? If on Windows, what OS version is in
use?
>
> There is another assert test that detects if the close is executed twice
> and this situation was not detected first. Therefore, I am guessing that
> one of the following is the cause.
>
> o OS related problems with closing a valid socket
> o the data structures employed by the CA client library have been
corrupted
> o CA client library object files are not all compiled with the same
version of
> the header files. This might occur if the header files updated on windows
and
> a complete rebuild is not completed with "make rebuild" or "make clean"
followed
> by "make".
>
> Is this problem easily reproducible? Is it intermittent?
>
> Jeff
>
>
>
>



References:
RE: ca assert Jeff Hill

Navigate by Date:
Prev: RE: ca assert Jeff Hill
Next: DM/EDD and Redhat Linux Chestnut, Ronald P.
Index: 1994  1995  1996  1997  1998  1999  2000  <20012002  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: ca assert Jeff Hill
Next: DM/EDD and Redhat Linux Chestnut, Ronald P.
Index: 1994  1995  1996  1997  1998  1999  2000  <20012002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·