I have now reproduced this with a small example.  The trace is a bit
shorter - it ends with a call on Void target in {STD_BYTE_CODE}.formulate_inherited_assertions
but I'm certain it is the same bug.

Added eweasel test incr342 for this bug.