From 092746d36a88d415960864dab034bb83b4bd4d8d Mon Sep 17 00:00:00 2001 From: Marty Kraimer Date: Wed, 6 Aug 2003 18:18:40 +0000 Subject: [PATCH] more bug changes --- RELEASE_NOTES.html | 25 ++++++++++++++++++++++++- 1 file changed, 24 insertions(+), 1 deletion(-) diff --git a/RELEASE_NOTES.html b/RELEASE_NOTES.html index edce85ab7..7eab7eb3c 100644 --- a/RELEASE_NOTES.html +++ b/RELEASE_NOTES.html @@ -20,7 +20,6 @@ CMLOG, will now receive the logMsg messages.

Previously if a dbGetLink failed on one of the input links, dbGetLink was not called for the remaining links. Now it is.

-

put notify

put notify did not act properly if a record had disp=TRUE, i.e. if puts are disabled. It now returns S_db_putDisabled.

@@ -77,6 +76,30 @@ 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).

+

macLib

+ +

macParseDefns did not check for handle==NULL. The documentation for +macParseDefns was not correct.

+ +

task_params.h

+

"event task" changed tp "event_task".

+ +

drvGpib

+

Remove some dead code. +Clean up code for handling A24 DMA memory.

+ +

dbGetLink and dbPutLink

+

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 +steps:

+
    prset->get_array_info(paddr,&no_elements,&offset);
+    write nNew elements into array >>
+    prset->put_array_info(paddr,nNew);
+ +

This sets NORD = nNew. But because of the dbGetLink bug, the soft device +support attached to the waveform record sets NORD to NELM.

+

This problem is fixed. The actual bug was in macros in dbAccess.h

Changes since 3.13.7

dbEvent Bug Fix Changes