Merge ~bhill/epics-base:db-tpro-show-values into ~epics-core/epics-base/+git/epics-base:3.16
Proposed by
Bruce Hill
| Status: | Needs review |
|---|---|
| Proposed branch: | ~bhill/epics-base:db-tpro-show-values |
| Merge into: | ~epics-core/epics-base/+git/epics-base:3.16 |
| Diff against target: |
168 lines (+48/-0) 11 files modified
src/std/rec/aSubRecord.c (+2/-0) src/std/rec/aiRecord.c (+4/-0) src/std/rec/aoRecord.c (+4/-0) src/std/rec/biRecord.c (+6/-0) src/std/rec/boRecord.c (+5/-0) src/std/rec/calcRecord.c (+5/-0) src/std/rec/calcoutRecord.c (+5/-0) src/std/rec/longinRecord.c (+4/-0) src/std/rec/longoutRecord.c (+4/-0) src/std/rec/mbbiRecord.c (+4/-0) src/std/rec/mbboRecord.c (+5/-0) |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Andrew Johnson | Needs Fixing | ||
| Ralph Lange | Needs Fixing | ||
|
Review via email:
|
|||
Description of the change
Add diagnostic support for showing record values when TPRO is >= 2
To post a comment you must log in.

See previous discussion at https:/ /github. com/epics- base/epics- base/pull/ 20
I personally like the idea of using TPRO to control debug prints. So much so that I've been adding it to my drivers so the last couple of years.
I don't have a problem with overloading TPRO in this way in Base. I would make the threshold numbers it larger (5 and 10).
As this is Base, maybe we should add a new field instead? Is .DDBG taken (aka Device support DeBuG)?