Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#968670: dwz: Fails with "Unknown DWARF DW_OP_1"
162 views
Skip to first unread message
Diego López León
Aug 19, 2020, 9:00:03 AM8/19/20
to
Package: dwz
Version: 0.13-5
Severity: normal
X-Debbugs-Cc: qdco...@relay.firefox.com
Hi,
I'm building a package for the liboqs library, a post quantum algorithms library,
for being proposed to be included in the archives, and when I run the build it fails with
"Unknown DWARF DW_OP_1".
This package can be built using Docker and I let a commit with the broken state at
https://github.com/lacchain/liboqs-debian/commit/4823333cb19fcca9449b286bb597b9b0e14ba0b7
I can provide the liboqs shared library on request if you can't reproduce it.
Best regards,
Diego
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.76-linuxkit (SMP w/4 CPU threads)
Kernel taint flags: TAINT_RANDSTRUCT
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
Versions of packages dwz depends on:
ii libc6 2.31-1
ii libelf1 0.176-1.1
dwz recommends no packages.
dwz suggests no packages.
-- no debconf information
Version: 0.13-5
Severity: normal
X-Debbugs-Cc: qdco...@relay.firefox.com
Hi,
I'm building a package for the liboqs library, a post quantum algorithms library,
for being proposed to be included in the archives, and when I run the build it fails with
"Unknown DWARF DW_OP_1".
This package can be built using Docker and I let a commit with the broken state at
https://github.com/lacchain/liboqs-debian/commit/4823333cb19fcca9449b286bb597b9b0e14ba0b7
I can provide the liboqs shared library on request if you can't reproduce it.
Best regards,
Diego
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.76-linuxkit (SMP w/4 CPU threads)
Kernel taint flags: TAINT_RANDSTRUCT
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
Versions of packages dwz depends on:
ii libc6 2.31-1
ii libelf1 0.176-1.1
dwz recommends no packages.
dwz suggests no packages.
-- no debconf information
Dennis Filder
Feb 6, 2021, 3:00:04 AM2/6/21
to
Control: tag -1 - patch + moreinfo
After looking into this some more, I don't think this is necessarily a
bug in dwz, but it could also be either someone using rogue DW_OP_*
definitions with values 0x00 and 0x01 or a buggy compiler/assembler
backend emitting junk. While applying the patch probably won't hurt,
it will most probably not help either.
@Diego: Could you still provide us with the unstripped shared library?
That would make tracking this down much easier.
Regards,
Dennis
After looking into this some more, I don't think this is necessarily a
bug in dwz, but it could also be either someone using rogue DW_OP_*
definitions with values 0x00 and 0x01 or a buggy compiler/assembler
backend emitting junk. While applying the patch probably won't hurt,
it will most probably not help either.
@Diego: Could you still provide us with the unstripped shared library?
That would make tracking this down much easier.
Regards,
Dennis
Andrius Merkys
Sep 17, 2021, 11:30:03 AM9/17/21
to
Control: found -1 0.14-1
Control: block 994548 by -1
Hello,
I am attempting building liboqs 0.7.0 and also experiencing this bug. My
packaging attempt is here [1]. After having read the discussion here and
on upstream tracker [2] I am of opinion that libiberty might have gotten
out of sync again, but I may be wrong.
[1] https://salsa.debian.org/merkys/liboqs
[2] https://sourceware.org/bugzilla/show_bug.cgi?id=27357
Andrius
Control: block 994548 by -1
Hello,
I am attempting building liboqs 0.7.0 and also experiencing this bug. My
packaging attempt is here [1]. After having read the discussion here and
on upstream tracker [2] I am of opinion that libiberty might have gotten
out of sync again, but I may be wrong.
[1] https://salsa.debian.org/merkys/liboqs
[2] https://sourceware.org/bugzilla/show_bug.cgi?id=27357
Andrius
Michael Tokarev
May 8, 2022, 3:40:03 AM5/8/22
to
On Sat, 6 Feb 2021 08:54:57 +0100 Dennis Filder <d.fi...@web.de> wrote:
> Control: tag -1 - patch + moreinfo
>
> After looking into this some more, I don't think this is necessarily a
> bug in dwz, but it could also be either someone using rogue DW_OP_*
> definitions with values 0x00 and 0x01 or a buggy compiler/assembler
> backend emitting junk. While applying the patch probably won't hurt,
> it will most probably not help either.
This prob now started appearing on ppc64el and s390x buildds on regular
> Control: tag -1 - patch + moreinfo
>
> After looking into this some more, I don't think this is necessarily a
> bug in dwz, but it could also be either someone using rogue DW_OP_*
> definitions with values 0x00 and 0x01 or a buggy compiler/assembler
> backend emitting junk. While applying the patch probably won't hurt,
> it will most probably not help either.
bullseye builds, f.e.
https://buildd.debian.org/status/fetch.php?pkg=qemu&arch=s390x&ver=1%3A7.0%2Bdfsg-2%7Ebpo11%2B1&stamp=1651985111&raw=0
https://buildd.debian.org/status/fetch.php?pkg=qemu&arch=ppc64el&ver=1%3A7.0%2Bdfsg-2%7Ebpo11%2B1&stamp=1651980296&raw=0
dh_dwz -a -a
dwz: debian/qemu-system-misc/usr/bin/qemu-system-alpha: Unknown DWARF DW_OP_0
dwz: debian/qemu-system-misc/usr/bin/qemu-system-hppa: Unknown DWARF DW_OP_0
dwz: debian/qemu-system-misc/usr/bin/qemu-system-riscv32: Unknown DWARF DW_OP_0
dwz: debian/qemu-system-misc/usr/bin/qemu-system-riscv64: Unknown DWARF DW_OP_0
dwz: debian/qemu-system-misc/usr/bin/qemu-system-s390x: Unknown DWARF DW_OP_0
dwz: debian/qemu-system-misc/usr/bin/qemu-system-sh4: Unknown DWARF DW_OP_0
dwz: debian/qemu-system-misc/usr/bin/qemu-system-sh4eb: Unknown DWARF DW_OP_0
dwz: debian/qemu-system-misc/usr/bin/qemu-system-xtensa: Unknown DWARF DW_OP_0
dwz: debian/qemu-system-misc/usr/bin/qemu-system-xtensaeb: Unknown DWARF DW_OP_0
dh_dwz: error: dwz -mdebian/qemu-system-misc/usr/lib/debug/.dwz/powerpc64le-linux-gnu/qemu-system-misc.debug
-M/usr/lib/debug/.dwz/powerpc64le-linux-gnu/qemu-system-misc.debug -- debian/qemu-system-misc/usr/bin/qemu-system-alpha
debian/qemu-system-misc/usr/bin/qemu-system-avr debian/qemu-system-misc/usr/bin/qemu-system-cris debian/qemu-system-misc/usr/bin/qemu-system-hppa
debian/qemu-system-misc/usr/bin/qemu-system-m68k debian/qemu-system-misc/usr/bin/qemu-system-microblaze
debian/qemu-system-misc/usr/bin/qemu-system-microblazeel debian/qemu-system-misc/usr/bin/qemu-system-nios2
debian/qemu-system-misc/usr/bin/qemu-system-or1k debian/qemu-system-misc/usr/bin/qemu-system-riscv32
debian/qemu-system-misc/usr/bin/qemu-system-riscv64 debian/qemu-system-misc/usr/bin/qemu-system-rx debian/qemu-system-misc/usr/bin/qemu-system-s390x
debian/qemu-system-misc/usr/bin/qemu-system-sh4 debian/qemu-system-misc/usr/bin/qemu-system-sh4eb debian/qemu-system-misc/usr/bin/qemu-system-tricore
debian/qemu-system-misc/usr/bin/qemu-system-xtensa debian/qemu-system-misc/usr/bin/qemu-system-xtensaeb returned exit code 1
make[1]: *** [debian/rules:636: install-arch] Error 25
(it is DW_OP_0 not DW_OP_1, but since the above note suggests both
should not be seen "in wild", maybe these are related).
Is dwz or compiler broken on bullseye?
Thanks,
/mjt
Michael Tokarev
May 8, 2022, 4:40:03 AM5/8/22
to
It is the same on arm64 too, eg:
https://buildd.debian.org/status/package.php?p=qemu&suite=bullseye-backports
/mjt
https://buildd.debian.org/status/package.php?p=qemu&suite=bullseye-backports
/mjt
Andrius Merkys
Aug 7, 2022, 1:20:04 AM8/7/22
to
Control: affects - src:liboqs
Hello,
src:liboqs/0.7.2~rc1-1 is no longer affected by this bug anymore.
Andrius
Hello,
src:liboqs/0.7.2~rc1-1 is no longer affected by this bug anymore.
Andrius
0 new messages