3 ms·
>"The only thing that jumped out to me was the appearance of a sync word at the beginning of each packet, 0xf0debc0a. (In little endian, this is 0x0abcdef0.) On
by peter_d_sherman 6y ago
>"The only thing that jumped out to me was the appearance of a sync word at the beginning of each packet, 0xf0debc0a. (In little endian, this is 0x0abcdef0.) On a lark, I Googled this, and actually found a project on GitHub from 2015..."
That is some excellent Google-Fu!
I had never thought about Googling the reversed-endian versions of hexadecimal constants -- until you wrote about doing this; I think it's a brilliant idea, so I'm adding it to my search engine technique toolbox.
In summation, it's a great idea!
It's both simple and elegant!
- londons_explore 6y agoWhat surprises me is that there aren't more users of this constant...
- ejolto 6y agoI usually see constants that are easier to read like 0xdeadbeef, 0x0c0ffee0 or 0xcafecafe
- archi42 6y agoAlso works with function names: I regularly read assembly for which I don't have the source, only debug info. If the routine I'm interested in looks like a library or framework, there is some chance it's open source - so I'll throw it into Google and see what it brings up. Even if I don't get the exact same source (e.g. don't know the exact libc version), I get an idea what the routine should do, which tremendously cuts the time I need to understand what's going on.