Story

On air. The free wire runs 15 minutes behind live. See pricing

World, crypto, finance and tech news, scored for impact.

TechHacker NewsFiled 4 days ago

Paths in pieces

Open the sourceReported by Hacker News, stoppels.ch, 12 November 2026

Not investment advice. Muhabbit scores how much a story may matter, not which way to trade.

GCC 12 and later can split string constants into overlapping 16-byte fragments loaded into xmm registers, so absolute build paths embedded via `std::string`, `strcpy` or `memcpy` may not appear literally in compiled x86-64 binaries. In a worked example, a binary built from a `std::string` holding `/home/linuxbrew/.linuxbrew` contained that path zero times under both `grep` and `strings`, instead surfacing the misleading fragment `/home/linuxbrew/xbrew/.linuxbrew`. The behavior affects Linux distributions and package managers that audit just-built binaries for non-relocatable paths, since pointer-only uses such as `fopen(PREFIX "/x", "r")` remain intact while copied strings do not. It also complicates relocation schemes used by Conda and Spack, which install into padded prefixes and patch binaries in place, with Conda relying on a repeated `_placehold` directory name to keep prefixes long enough. The practical upshot is that simple `grep` or `strings` checks can miss embedded build paths entirely. Watch for tooling that inspects binaries at the instruction or section level rather than scanning raw bytes, and for guidance to package managers on validating relocatability.

Muhabbit's AI wrote this summary in its own words from Hacker News's report. It can get details wrong, so check the source.

Named in this story

GCC, Linux, GNU binutils, x86-64