On 12/11/2017 09:51 AM, Dave Mitchell wrote:
On Mon, Dec 11, 2017 at 12:52:35PM +0000, Yaroslav Kuzmin wrote:
Log availabel at
https://drive.google.com/file/d/1BwOR2pbtYRTJ4TqWMh33FtD9PZahf1HM<https://drive.google.com/file/d/1BwOR2pbtYRTJ4TqWMh33FtD9PZahf1HM/view?usp=sharing>
Unfortunately that run didn't trigger the failure code which has heavy
instrumentation attached. It turns out that there are 5 places in the test
script that do an eval and might fail. The attached davem2 script
instruments all 5 evals.
I would be grateful if you could run it.
It is likely that the reason the failure code was not triggered this
time is that it was changed somewhat by the addition of the
instrumentation code. My guess, without knowing how anything works
here, is that the mention of the variables being debugged causes them to
not be optimized away.
