The data in question is part of the USDT probe data that is stored in ELF notes. It puts the utsname data in there because that helps identify the system where the library or executable with the probes was built. It is not functional information, but rather informative in case issues with the USDT data need to be debugged. In that sense it is perhaps more akin to including gcc version in executables, etc.
Since it is information only, it is not meant to be reproducible across systems, which clearly runs afoul with the reproduced processing. Ideally, it should be something that can be ignored because it is not functionally different. I can opt to exclude it from being generated but I would expect that similar issues can pop up elsewhere as well since ELF note data like that can depend on things that will differ between systems where the artifacts are built. The executables in question in dtrace-tests are testsuite triggers that are only ever used in testsuite runs. For those executables, the data is not really important, but USDT probes can be compiled into any executable or library and there it can be quit4e beneficial to have this data available for debugging since such executables and libraries are typically deployed to different systems. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free.www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Jun 16, 2026 at 1:31 PM Debian Bug Tracking System < [email protected]> wrote: > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 1140167: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1140167. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > As you requested using X-Debbugs-CC, your message was also forwarded to > [email protected] > (after having been given a Bug report number, if it did not have one). > > Your message has been sent to the package maintainer(s): > [email protected] > > If you wish to submit further information on this problem, please > send it to [email protected]. > > Please do not send mail to [email protected] unless you wish > to report a problem with the Bug-tracking system. > > -- > 1140167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1140167 > Debian Bug Tracking System > Contact [email protected] with problems >
