Final field types not reported correctly (introduced by rev 12658)

Bug #1495417 reported by Ralph Lange
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
EPICS Base
Confirmed
Medium
Andrew Johnson

Bug Description

Revision 12658 was fixing a behaviour for LINK fields, but introduced a bug for other special fields.

The field_type of the probe that is sent through a filter chain represents the DBF type of the field update. The dbChannelFinalFieldType() macro returns this, while the dbChannelFinalCAType() macro is supposed to return the DBR type.

This came up as pvaSrv has to treat DBF_MENU and DBF_DEVICE special, but these field types are not visible anymore.
(See https://github.com/epics-base/pvaSrv/issues/17)

Tags: db
summary: - Special fields' types not reported correctly (introduced by rev 12658)
+ Final field types not reported correctly (introduced by rev 12658)
Revision history for this message
mdavidsaver (mdavidsaver) wrote :

I think this has now been fixed. Ralph, can you confirm?

Changed in epics-base:
assignee: nobody → Andrew Johnson (anj)
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Ralph Lange (ralph-lange) wrote :

Negative.

The downstream pvaSrv issue has been fixed using a workaround, this issue is still active.

Andrew Johnson (anj)
Changed in epics-base:
status: Incomplete → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.