X86 Lds May 2026

The offending line looked innocent:

The disassembly pointed to one instruction: LDS .

The GPF happened when LDS tried to read from DS:SI —but DS had been clobbered by an interrupt handler. So LDS cheerfully loaded garbage into DS itself, because that’s what LDS does: it writes the segment part of the loaded pointer directly into the DS register. Now DS pointed to an unmapped address. The next instruction—a simple mov ax, [bx] —caused the system to keel over. x86 lds

Eleanor muttered, “Oh, you ancient beast.”

In the spring of 1992, Eleanor, a young and slightly reckless systems programmer, found herself hunched over a beige 386 DX/40. The machine groaned under MS-DOS 5.0, and in front of her was a nightmare: a core dump from a geological modeling program she’d inherited. The offending line looked innocent: The disassembly pointed

She couldn’t just remove the LDS . The entire linked list traversal depended on far pointers. But she could replace it.

That night, Eleanor poured a whiskey and thought about LDS . Born in 1978 with the 8086, mature in the 286’s protected mode, and already a zombie on the 386—kept alive only by backward compatibility. It was the programming equivalent of a rotary phone in a smartphone world. You could still use it. But you really, really shouldn’t. Now DS pointed to an unmapped address

A decade later, she’d tell interns: “ LDS loads a pointer and destroys your data segment. Respect it. Then avoid it.”