I noticed that one of the appveyor runs triggering an assertion failure in printer.cpp. The MS documentation is clear enough:
The behavior of isprint and _isprint_l is undefined if c isn't EOF or in the range 0 through 0xFF, inclusive.
When a debug CRT l>ibrary is used and c isn't one of these values, the functions raise an assertion.
I noticed that one of the appveyor runs triggering an assertion failure in printer.cpp. The MS documentation is clear enough:
https://ci.appveyor.com/project/epics-base-7/epics-base/builds/45492554/job/5tauw07hyhd8qn22
This is pointing to
https://github.com/epics-base/pvDataCPP/blob/45671faaea4d091523350f6c111193ef0d103aa6/src/factory/printer.cpp#L485 ... https://github.com/epics-base/pvDataCPP/blob/45671faaea4d091523350f6c111193ef0d103aa6/src/factory/printer.cpp#L500