Use of bad TTData in search() when ttHit is false

[mstembera]

Describe the issue

As pointed out by @dubslow here #5416 (comment) and @peregrineshahin #5416 (comment) in some places search() uses values from TTData even when ttHit is false.

Expected behavior

Don't use any values from TTData when ttHit is false.

Steps to reproduce

Inspect Search::Worker::search() code.

Anything else?

No response

Operating system

All

Stockfish version

a8401e8

[peregrineshahin]

Regarding this issue, the LTC fix passed https://tests.stockfishchess.org/tests/view/66a243b14ff211be9d4ecd4a
but I'm not able to reproduce any trigger for these two places left "unguarded" with any testing condition/long benches (multithreaded included), I'm not sure that we are using any 'bad TTData in search() when ttHit is false' as of the moment.
It probably can be explained logically, but not too sure..

[mstembera]

Hmm I'm even less sure. Maybe open a PR for the fix as an RFC and see what the maintainers and others say?