Experimental Physics and
Industrial Control System

Seems like the best course is for dbProcess() and processTarget()
to keep track of which records are being recursed into.

I could see of a way around this by storing an identifier in the PUTF and RPRO fields which would let us see that (I'd make the PUTF and RPRO fields into DBF_LONG and use an atomic counter to generate a unique ID for each source put).

I was thinking of using a stack address, or maybe epicsThread*, from the thread which is doing
the processing.  Not really fundamentally different from a global counter, though maybe easier
to debug.  This would be set and cleared by dbProcess().

    else if (psrc->putf && psrc->putf != pdst->putf) {

# ===== Chain 2 again ======
ok 11 - dbPutField("chain2:1.B", 5, ...) -> 0 (Success)
ok 12 - dbPutField("chain2:1.B", 5, ...) -> 0 (Success)
ok 13 - dbPutField("chain2:1.B", 5, ...) -> 0 (Success)
Bail out! Processing timed out
Abort

I'm not sure about hijacking the existing flag fields.  Maybe add a new field in dbCommonPvt?

-- 
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon