At 11:58, she compiled the shim, injected it into the running loader process (dangerous—one wrong address and the entire OS would page fault), and held her breath.
[INFO] Import 'guidance.calc' resolved → guidance_calc_v3.dll (forced via shim) [INFO] All systems nominal. Proceeding to launch sequence.
Her blood turned cold.
Legacy? Version 2? The build server had purged v2 months ago. She had personally signed off on the deprecation notice. She ssh’d into the deployment image’s library directory.
The wrong DLL was physically present. The loader, following its ancient, stubborn rules, found a file matching the requested name and loaded it without checking version or content. The v2 DLL exported guidance.calc , yes—but with different parameter alignment and a fatal overflow bug in the horizon sensor fusion routine. At 11:58, she compiled the shim, injected it
Loaded C:\sys\lib\guidance_calc_legacy.dll — Version 2.1.4 (Build 0)
She slumped against the server rack, heart hammering. Her blood turned cold
But the loader had chosen the legacy file. Why?