News for hackers. Stuff that matters.
Re:You Can't Always Hash Pointers in C (2016) by quotemstr on Wednesday September 19, 2018 @02:52AM (#18022279)
Who said you need or want run-to-run hash stability? One common technique for defeating hash collision attacks is maxing a secret random tweak, newly computed on each program run, into to hash function. (Python is one environment that uses this trick.) Under this scheme, hash values are unstable, but the world keeps working. Hash stability turns out not to be particularly important most of the time.

Generally speaking, if your program depends on the stability of hash-table enumeration order, you're doing something wrong in the first place.

Re:You Can't Always Hash Pointers in C (2016) by delhanty on Wednesday September 19, 2018 @05:32AM (#18022980)
>if your program depends on the stability of hash-table enumeration order, you're doing something wrong in the first place

The point is not all programs are correct.

If you're trying to reproduce a bug that occurs in the release version, but goes away in the debug version (because hash-table enumeration order changes) that makes life more difficult.