CA communicates diagnostics three ways - why is that
Bug #541273 reported by
Jeff Hill
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
EPICS Base |
Invalid
|
Wishlist
|
Unassigned |
Bug Description
CA currently communicates diagnostics three ways:
1) exception callback
2) CA printf callback
3) errlogPrintf
The 2nd way arose because its not easy to force all diagnostic messages into an exception (the exception
callback needs a printf format and varargs).
The third way arose because there are certain situations where CA has a lock applied and it cant easily be released
before calling the printf handler. CA currently tries to never hold a lock when calling a callback.
See also #326
Original Mantis Bug: mantis-238
http://
tags: | added: cleanup |
Changed in epics-base: | |
status: | New → Invalid |
To post a comment you must log in.