Notes about issue captures_build_path_via_assert in unstable
|Suites:||stretch / buster / unstable / experimental|
Absolute paths to source file names are embedded through assert(), which
embeds the value of the __FILE__ macro in the .data section, or via
filenames in debug symbols, which shows in the .text and .debug_str sections.
We have a pending patch to GCC to fix this in one central place.
If/when this is accepted, this issue should be fixed for all packages and
you should not need to fix it specifically in your package.
For more background information see:
Packages in 'unstable' known to be affected by this issue:
(the 1/4 most-popular ones (within this issue) are underlined)
18 unreproducible packages in unstable/amd64:
1 FTBFS packages in unstable/amd64:
25 reproducible packages in unstable/amd64:
Our notes about issues affecting packages are stored in notes.git and are targeted at packages in Debian in 'unstable/amd64' (unless they say otherwise).
A package name displayed with a bold
font is an indication that this package has a note. Visited
packages are linked in green, those which have not been visited are
linked in blue.
# sign after the name of a package
indicates that a bug is filed against it. Likewise, a
+ sign indicates there is a
patch available, a
P means a
pending bug while
# indicates a
closed bug. In cases of several bugs, the symbol is repeated.