Your message dated Thu, 03 Oct 2019 20:38:41 +0000
with message-id <e1ig7s1-000goy...@fasolo.debian.org>
and subject line Bug#941559: fixed in xvidcore 2:1.3.5-2
has caused the Debian Bug report #941559,
regarding libxvidcore4: immediately crashes on amd64 since binNMU
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
941559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libxvidcore4
Version: 2:1.3.5-1
Severity: grave
Tags: sid bullseye
Hi,
Just over a month ago xvidcore was binNMUed and this seems to have
triggered a bug somewhere and now any application which tries to
initialize libxvidcore will segfault.
Test app:
#include <stddef.h>
#include <xvid.h>
int main(void)
{
xvid_gbl_init_t init = {
.version = XVID_VERSION,
.cpu_flags = 0,
.debug = 0,
};
xvid_global(NULL, XVID_GBL_INIT, &init, NULL);
return 0;
}
$ gcc -o xvid-test xvid-test.c -lxvidcore
$ ./xvid-test
Segmentation fault (core dumped)
The crash happens here:
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7f22940 in check_cpu_features () from
/usr/lib/x86_64-linux-gnu/libxvidcore.so.4
(gdb) bt
#0 0x00007ffff7f22940 in check_cpu_features () from
/usr/lib/x86_64-linux-gnu/libxvidcore.so.4
#1 0x00007ffff7e9c15b in detect_cpu_flags () at ../../src/xvid.c:156
#2 0x00007ffff7e9d265 in xvid_gbl_init (init=0x7fffffffdee4,
init=0x7fffffffdee4) at ../../src/xvid.c:793
#3 xvid_global (handle=<optimized out>, opt=<optimized out>,
param1=0x7fffffffdee4, param2=<optimized out>) at ../../src/xvid.c:816
#4 0x000055555555516d in main ()
Which in turn seems to happen because the check_cpu_features function is
in a non-executable read only memory region.
$ /proc/4658/maps
[...]
7ffff7e87000-7ffff7e8b000 rw-p 00000000 00:00 0
7ffff7e8b000-7ffff7e8d000 r--p 00000000 fd:00 954232
/usr/lib/x86_64-linux-gnu/libxvidcore.so.4.3
7ffff7e8d000-7ffff7ef5000 r-xp 00002000 fd:00 954232
/usr/lib/x86_64-linux-gnu/libxvidcore.so.4.3
[vvv]
7ffff7ef5000-7ffff7f2b000 r--p 0006a000 fd:00 954232
/usr/lib/x86_64-linux-gnu/libxvidcore.so.4.3
[^^^]
7ffff7f2b000-7ffff7f2c000 r--p 0009f000 fd:00 954232
/usr/lib/x86_64-linux-gnu/libxvidcore.so.4.3
7ffff7f2c000-7ffff7f36000 rw-p 000a0000 fd:00 954232
/usr/lib/x86_64-linux-gnu/libxvidcore.so.4.3
7ffff7f36000-7ffff7fa1000 rw-p 00000000 00:00 0
[...]
Indeed readelf contains some non-executable program headers in
2:1.3.5-1+b1 which do not appear in 2:1.3.5-1 in buster. The
".rotext" section sounds suspicious.
2:1.3.5-1+b1:
$ readelf -l /usr/lib/x86_64-linux-gnu/libxvidcore.so.4
[...]
Program Headers:
Type Offset VirtAddr PhysAddr
FileSiz MemSiz Flags Align
LOAD 0x0000000000000000 0x0000000000000000 0x0000000000000000
0x00000000000018a8 0x00000000000018a8 R 0x1000
LOAD 0x0000000000002000 0x0000000000002000 0x0000000000002000
0x00000000000673c9 0x00000000000673c9 R E 0x1000
LOAD 0x000000000006a000 0x000000000006a000 0x000000000006a000
0x0000000000035088 0x0000000000035088 R 0x1000
LOAD 0x000000000009fb90 0x00000000000a0b90 0x00000000000a0b90
0x00000000000098d0 0x0000000000073138 RW 0x1000
[...]
00 .note.gnu.build-id .gnu.hash .dynsym .dynstr .gnu.version
.gnu.version_r .rela.dyn .rela.plt
01 .init .plt .plt.got .text .fini
02 .rodata .rotext .eh_frame_hdr .eh_frame
03 .init_array .fini_array .data.rel.ro .dynamic .got .data .bss
2:1.3.5-1:
$ readelf -l /usr/lib/x86_64-linux-gnu/libxvidcore.so.4
[...]
Program Headers:
Type Offset VirtAddr PhysAddr
FileSiz MemSiz Flags Align
LOAD 0x0000000000000000 0x0000000000000000 0x0000000000000000
0x000000000009da50 0x000000000009da50 R E 0x200000
LOAD 0x000000000009db90 0x000000000029db90 0x000000000029db90
0x00000000000098d0 0x0000000000073138 RW 0x200000
[...]
00 .note.gnu.build-id .gnu.hash .dynsym .dynstr .gnu.version
.gnu.version_r .rela.dyn .rela.plt .init .plt .plt.got .text .fini .rodata
.rotext .eh_frame_hdr .eh_frame
01 .init_array .fini_array .data.rel.ro .dynamic .got .data .bss
James
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: xvidcore
Source-Version: 2:1.3.5-2
We believe that the bug you reported is fixed in the latest version of
xvidcore, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 941...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Fabian Greffrath <fab...@debian.org> (supplier of updated xvidcore package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Thu, 03 Oct 2019 21:38:53 +0200
Source: xvidcore
Architecture: source
Version: 2:1.3.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers <debian-multime...@lists.debian.org>
Changed-By: Fabian Greffrath <fab...@debian.org>
Closes: 941559
Changes:
xvidcore (2:1.3.5-2) unstable; urgency=medium
.
[ Ondřej Nový ]
* d/copyright: Change Format URL to correct one
.
[ Felipe Sateler ]
* Change maintainer address to debian-multime...@lists.debian.org
.
[ Ondřej Nový ]
* Use debhelper-compat instead of debian/compat
.
[ Fabian Greffrath ]
* Define a standard ELF .text section in ASM code,
instead of .rotext (Closes: #941559).
* Bump Standards-Version to 4.4.0.
* Bump debhelper-compat to 12.
* Add Rules-Requires-Root: no.
* Add Build-Depends-Package line to symbols file.
* Fix invalid control statement in debian/control.
* Install examples in ibxvidcore-dev package.
Checksums-Sha1:
d65cd4361e125b94913b1da3e13174e808d4ac23 2120 xvidcore_1.3.5-2.dsc
39c312755a94828e46e94480b9434e6b82f969dd 6664 xvidcore_1.3.5-2.debian.tar.xz
ee6f2716443c3ab8c61e67fd88eb7d2504ba382f 5955 xvidcore_1.3.5-2_amd64.buildinfo
Checksums-Sha256:
f026f265244283fab6da4fc38e8aa472d5c26b9384bb762bbf19a7d42a2d0c95 2120
xvidcore_1.3.5-2.dsc
a60f59c200e0c451a96cae6d2fee80737403c00723cc522067a2300e059d3c77 6664
xvidcore_1.3.5-2.debian.tar.xz
cb342789f6e418b51e61c4a23b796d38a5038026a239917d247991b122d0cb87 5955
xvidcore_1.3.5-2_amd64.buildinfo
Files:
52ddc189321f4185be6b0c47e345aa8e 2120 libs optional xvidcore_1.3.5-2.dsc
29b9d20438b6519560ee6da61a148d4f 6664 libs optional
xvidcore_1.3.5-2.debian.tar.xz
d53e43427179de64a13650b08ec4135d 5955 libs optional
xvidcore_1.3.5-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJGBAEBCAAwFiEEIsF2SKlSa4TfGRyWy+qOlwzNWd8FAl2WTvoSHGZhYmlhbkBk
ZWJpYW4ub3JnAAoJEMvqjpcMzVnfNGsP/0qJNsNgGCkFoZmzQYftIBmlQzWlGICt
CBZWhgItUL9aH9ShCkAqO3bldFs35za9nYkWN5NJmNAtx3JJk6ISCcYbuP/Qzzbv
esSLI1VJGfxfRiqzAA2ZjgeaP5gVf1inrieOKqEzTnnbfKXkt1JzbPykUKDjdJar
+qdRDiZfU7SarZjj/YCvVvmC0CktFrM1E0b1c1C0+4/+pTFc7NZT0+9p9qYZMW2n
ZEag0NbK/uzAYzyoJAkKoSxdc1UnfKywWMHVuUHHvQYRWpljzWlkua/DEVuOJs2J
/mv9hTtJJLWUkwkZoe4RA0aqCR3My1/YsVeN+xr+ZKcC5Sgt76zlM0SEDiKMV2LI
qUNqstLcmJucGNvFt2Qm7XZ5WxhltA9Ls5GQFIWkYaihLq1dl0os375QIFj7hQnH
+KjP3CvrRj0gH8Msz27XvMn1Qvo2Ec42TWYahtLEe9Py768RHMN8XJIPLcXnlucH
m5zJ+DGbbbUi2L7+NOwCQCPrPoew5MhbDciRamxlzUBbQATmGzxva1WJho3q1DlQ
ZZLAEKm6vXwts7Tty0LKFxQ9XSwqhMTwH4RDBM7krdAPPN/qOb6Vk5DN9EC6S+oF
gq0qLHK30kRy3OaYMZz8QBajDiPyK6vLg5RF7rkMhVbi6TENXZQRxuGrffL8VpNp
BdITj6/f6ZsU
=4H1j
-----END PGP SIGNATURE-----
--- End Message ---
