You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix optImpliedByTypeOfAssertions to correctly find a non-null assertion (#120917)
Fixes#120792
This looks like some very old bug that was exposed by an unrelated
change in .NET 10.0
Basically, we have an assertion `obj->pMT == <cns_type>` we invoke
`optImpliedByTypeOfAssertions` to see if we can find some existing
assertion (anywhere) for `obj != null` so we can duplicate it into
current `ASSERT_TP& activeAssertions`, because `obj->pMT` assertion
implies obj is not null.
We do find such an assertion but for some reason we don't check that
it's null on the right side (op2) -> obj != null. Instead, we pick up
some random `obj != <frozen_object>` assertion which then is incorrectly
used.
[No
diffs.](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1180340&view=ms.vss-build-web.run-extensions-tab)
0 commit comments