Hunting a 34 year old pointer bug in EtherSlip
32 points by mbbrutman 3 days ago | 4 comments
kazinator 4 hours ago
> ** NULL assignment detected
replyThat's without any hardware support (MMU) on DOS; compiler-generated code does the null checks.
Without it, you get unpredictable results for that bit of UB; the program can trample bytes around the null address.
NooneAtAll3 5 hours ago
I wonder if you could've tried "Fil-C" compiler to catch the bug
replyone of those things that "I heard about recently, would love a practical test, but have no current need to try on"
Today, the same is true of many other physical-layer protocols that developed later, such as WiFi and the GSMA mobile standards; they seem to have converged on the Ethernet frame format at the software interface, presenting the appearance of an Ethernet NIC to software, because that's the easiest way to make use of existing network stacks. There's also the weirdness of tunneling protocols like PPPoE which only exist to tunnel Ethernet through non-Ethernet systems.
Mobitex has three-byte addresses, like the vendor space of Ethernet, so I just picked some OUI (or was it just three null bytes?)