fixed redundant logFdAdd deadlock message

This commit is contained in:
Jeff Hill
2003-08-06 21:59:56 +00:00
parent 092746d36a
commit 0e47da7e57

View File

@@ -10,19 +10,16 @@
<h1>EPICS Release 3.13.9</h1>
<h2>Changes since 3.13.8</h2>
<h3>errlog and logMsg</h3>
<p>If logMsg was called by netTask it could cause the
ioc to hang.
To fix this problem the method of trapping logMsg calls has been changed.
The fix also means that any code that calls errlogAddListener, e.g.
CMLOG, will now receive the logMsg messages.</p>
<h3>calcRecord and calcoutRecord</h3>
<p>Previously if a dbGetLink failed on one of the input links, dbGetLink
was not called for the remaining links. Now it is.</p>
<p>Previously if a dbGetLink failed on one of the input links, dbGetLink was
not called for the remaining links. Now it is.</p>
<h3>put notify</h3>
<p>put notify did not act properly if a record had disp=TRUE, i.e.
if puts are disabled. It now returns S_db_putDisabled.</p>
<p>put notify did not act properly if a record had disp=TRUE, i.e. if puts
are disabled. It now returns S_db_putDisabled.</p>
<h3>Close-On-Exec flag set for all sockets created in EPICS base</h3>
@@ -36,7 +33,6 @@ This step was no longer required and therefore was removed from the code.</p>
<h3>Assert fail in CA libraries when system runs low on mbufs</h3>
<h4>Scope</h4>
<p>The bug exists in probably in all previous versions of EPICS.</p>
@@ -74,7 +70,8 @@ create a specialized vxWorks device driver which calls errlogPrintf for each
incoming message and then call logFdAdd for a file descriptor opened with
that device driver. The desirable functional change being errlogPrintf's
capability to discard messages when it gets behind (because of a transient
mbuf starvation situation).</p>
mbuf starvation situation). The fix also means that any code that calls
errlogAddListener, e.g. CMLOG, will now receive the logMsg messages.</p>
<h3>macLib</h3>
@@ -82,13 +79,15 @@ mbuf starvation situation).</p>
macParseDefns was not correct.</p>
<h3>task_params.h</h3>
<p>"event task" changed tp "event_task".</p>
<h3>drvGpib</h3>
<p>Remove some dead code.
Clean up code for handling A24 DMA memory.</p>
<p>Remove some dead code. Clean up code for handling A24 DMA memory.</p>
<h3>dbGetLink and dbPutLink</h3>
<p>A bug in dbGetLink resulted in nRequest not being given the value 0 if the
link is a constant link. This in turn caused the waveform record to always
set NORD=NELEM. Thus if an application trys to write a waveform via the
@@ -99,7 +98,9 @@ steps:</p>
<p>This sets NORD = nNew. But because of the dbGetLink bug, the soft device
support attached to the waveform record sets NORD to NELM.</p>
<p>This problem is fixed. The actual bug was in macros in dbAccess.h</p>
<h2>Changes since 3.13.7</h2>
<h3>dbEvent Bug Fix Changes</h3>