Pc-lint Plus Se -

Total errors: 1 Total warnings: 0 Bugs found that would have escaped unit test: 1 Lives potentially saved: unknown She closed the laptop. The ghosts, for now, were quiet.

That night, as she packed up, Eleanor looked at her terminal—still open, still showing PC-lint Plus SE’s final summary: pc-lint plus se

“We can’t. But we also can’t afford a drone that falls out of the sky. I’ll pull strings.” Two hours later, a license file landed in her inbox. Eleanor downloaded the tool, a command-line beast with no GUI, just a configuration file that looked like an ancient spellbook. She spent the next hour tuning it: setting the dialect to C17, enabling MISRA C:2023, turning on the aggressive interprocedural analysis, and—her final gambit—flipping on . Total errors: 1 Total warnings: 0 Bugs found

nav_sensor.c(412): error 4150: (Severe -- Semantic dataflow) Pointer 'temp_ptr' derived from 'sensor_buffer + offset' where offset is tainted by unvalidated CAN bus input (path: can_rx_handler -> validate_crc -> extract_payload -> compute_offset). Alias set analysis shows 'temp_ptr' and 'calib_ptr' may converge after loop unrolling at line 408, leading to write-write conflict when temperature exceeds 85°C. [Reference: CWE-123, MISRA C:2023 Rule 11.9] Eleanor froze. She scrolled up. The analyzer had traced a data flow across seven functions, through three files, and had identified not just a memory corruption, but the exact temperature threshold where it would manifest. But we also can’t afford a drone that falls out of the sky

Hank nodded. “PC-lint Plus SE doesn’t just find bugs. It finds intentions . It sees the ghosts in the machine—the paths your code could take, even if it never has before.”

“The issue isn’t the hardware,” Eleanor said, rubbing her eyes. “It’s the software. There’s a pointer dereference that only corrupts memory when the temperature sensor hits a specific threshold. I’ve run every static analyzer we own. Nothing catches it.”