Hello:
It looks like new dwz-0.13-6.fc34 is silently segfaulting when rebuilding some srpm, but it does not prevent whole rpmbuild process from stopping.
Some random example: * vorbis-tools-1.4.2-1.fc34 https://koji.fedoraproject.org/koji/buildinfo?buildID=1672461 x86_64 build log: https://kojipkgs.fedoraproject.org//packages/vorbis-tools/1.4.2/1.fc34/data/...
* rpm-4.16.1.2-4.fc34 https://koji.fedoraproject.org/koji/buildinfo?buildID=1672480 x86_64 build log: https://kojipkgs.fedoraproject.org//packages/rpm/4.16.1.2/4.fc34/data/logs/x...
Since rpmbuild process seems to finish anyway, this can be ignored?? (I guess not)
Regards, Mamoru
* Mamoru TASAKA:
It looks like new dwz-0.13-6.fc34 is silently segfaulting when rebuilding some srpm, but it does not prevent whole rpmbuild process from stopping.
This might be:
dwz crashes on DWARF5 line table with zero files https://bugzilla.redhat.com/show_bug.cgi?id=1919243
Would you please try and see if dwz-0.13-7.fc34 fixes the issue?
Since rpmbuild process seems to finish anyway, this can be ignored??
Historically, this is how dwz and gdb-add-index have been deployed. The idea is that failed debuginfo optimization do not make the package unusuable. (gdb-add-index crashes can lead to packaging of huge temporary files though.)
I'm not sure if this is the right approach anymore. If these tools cannot process the debuginfo, the debuginfo itself might be corrupted.
Thanks, Florian
Florian Weimer wrote on 2021/01/22 22:42:
- Mamoru TASAKA:
It looks like new dwz-0.13-6.fc34 is silently segfaulting when rebuilding some srpm, but it does not prevent whole rpmbuild process from stopping.
This might be:
dwz crashes on DWARF5 line table with zero files https://bugzilla.redhat.com/show_bug.cgi?id=1919243
Would you please try and see if dwz-0.13-7.fc34 fixes the issue?
Looks like at least for these 2 packages, dwz is no longer segfaulting, Thank you.
Since rpmbuild process seems to finish anyway, this can be ignored??
Historically, this is how dwz and gdb-add-index have been deployed. The idea is that failed debuginfo optimization do not make the package unusuable. (gdb-add-index crashes can lead to packaging of huge temporary files though.)
Okay, I didn't know this, thank you.
I'm not sure if this is the right approach anymore. If these tools cannot process the debuginfo, the debuginfo itself might be corrupted.
Thanks, Florian
Regards, Mamoru
Hi Mamoru,
On Fri, 2021-01-22 at 22:27 +0900, Mamoru TASAKA wrote:
It looks like new dwz-0.13-6.fc34 is silently segfaulting when rebuilding some srpm, but it does not prevent whole rpmbuild process from stopping.
Some random example:
- vorbis-tools-1.4.2-1.fc34 https://koji.fedoraproject.org/koji/buildinfo?buildID=1672461 x86_64 build log:
I just noticed that too and filed: https://bugzilla.redhat.com/show_bug.cgi?id=1919243
Since rpmbuild process seems to finish anyway, this can be ignored?? (I guess not)
It doesn't break the build, but it does make the debuginfo packages bigger than necessary. So please do report such issues in bugzilla.
I just came up with a patch and build dwz-0.13-7.fc34 which should fix this problem. https://bodhi.fedoraproject.org/updates/FEDORA-2021-7198012a4d
Cheers,
Mark