Open andrewl102 opened 4 years ago
I have a copy of a misapplied place locally that I somehow made that matches the md5 sum of the expected patch output from the latest commit to master for 10.14.6.
md5 CoreDisplay.bin MD5 (CoreDisplay.bin) = d4f2aca73c7915c639dbe9a7b9cf5ecd
(exactly the expected value of a successful d4f2aca73c7915c639dbe9a7b9cf5ecd '10.14.6 (18G84)')
d4f2aca73c7915c639dbe9a7b9cf5ecd '10.14.6 (18G84)'
otool -t CoreDisplay.bin |tail -n +2 |md5 -q 105051509e563ba96f190ed78a52feb9
(still the original value, and the one used in the source check)
hexdump CoreDisplay.bin | grep -i "bb 01 00 00 00 A8 01 0f 85" 00187c0 20 bb 01 00 00 00 a8 01 0f 85 8a 07 00 00 49 89
hexdump CoreDisplay.bin | grep -i "31 DB 90 90 90 90 90 90 E9" -> nothing
It looks like this was just a bad patch that was applied?
Correct hash is 450241a06a439cd226c9e9cf5cf634d7
I have a copy of a misapplied place locally that I somehow made that matches the md5 sum of the expected patch output from the latest commit to master for 10.14.6.
(exactly the expected value of a successful
d4f2aca73c7915c639dbe9a7b9cf5ecd '10.14.6 (18G84)'
)(still the original value, and the one used in the source check)
It looks like this was just a bad patch that was applied?