From: Ralph Lange <[email protected]> Sent: Wednesday, September 26, 2018 6:41 AM To: Williams Jr., Ernest L. Cc: EPICS Core Talk; Straumann, Till; Kim, Kukhee Subject: Re: Bug: #1790723 and Bug #1790715
Hi Ernest,
As far as I can see, the status information in the Launchpad issue tracker is up to date and should answer your questions.
Cheers,
~Ralph
On Tue, 25 Sep 2018 at 20:10, Williams Jr., Ernest L. <[email protected]> wrote:
Hi Ralph,
Now, that CloudBees is back in business.
I was hoping to pick up fixes for the following issues:
Until and including 3.15 -- (I didn't look at 3.16) the parameter string '@<parameter>' was an optional part of hardware link fields. In V7 this no longer seems to be the case dbStaticLib:2320: if (parm && pinfo->ltype != RF_IO) { /* move
parm string to beginning of buffer */ memmove(pinfo->target, parm, len + 1); } else if (!parm && pinfo->ltype == RF_IO) { /* RF_IO, the string isn't needed at all */ free(pinfo->target); ...
We have a standard solution for differing setsockopt argument sizes, see the typedefs in libcom/ src/osi/ os/*/osdSock. h and the section above in client/udpiiu.cpp It might be Okay to re-use osiSockOptMcast Loop_t since it probably has the same size on all
targets, but for safety's sake I would probably define a new typedef.