[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1093688: marked as done (libcamera: please consider disabling libunwind integration)

Your message dated Mon, 27 Jan 2025 11:30:13 +0000
with message-id <E1tcNJl-00EcH9-C1@fasolo.debian.org>
and subject line Bug#1093688: fixed in libcamera 0.4.0-4
has caused the Debian Bug report #1093688,
regarding libcamera: please consider disabling libunwind integration
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 owner@bugs.debian.org
immediately.)


-- 
1093688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093688
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: libcamera
Severity: wishlist

libcamera has libunwind integration, which is currently enabled on
architectures where libunwind exists. It seems to be used to print better
backtraces on a fatal signal or assertion failure.

While nice to have, this doesn't seem hugely important: under normal
circumstances, libcamera shouldn't be crashing, and if it crashes due
to a bug, tools like systemd-coredump are a more reliable way to get
high-quality backtraces (without requiring the crashing process to still
be in a mostly-working state).

Meanwhile, libunwind has several unaddressed RC bugs.

The readme also suggests that if we have libdw (and glibc), there's no
benefit to also having libunwind:

> for improved debugging: [optional]
>         libdw-dev libunwind-dev
>
>         libdw and libunwind provide backtraces to help debugging assertion
>         failures. Their functions overlap, libdw provides the most detailed
>         information, and libunwind is not needed if both libdw and the glibc
>         backtrace() function are available.

So it might be a good idea to reduce the key package status of libunwind
by disabling the libunwind integration on all architectures, and instead
relying on libdw/backtrace() or post-mortem core dump analysis?

Thanks,
    Simon

--- End Message ---
--- Begin Message --- 
Source: libcamera
Source-Version: 0.4.0-4
Done: Dylan Aïssi <daissi@debian.org>

We believe that the bug you reported is fixed in the latest version of
libcamera, 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 1093688@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dylan Aïssi <daissi@debian.org> (supplier of updated libcamera 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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 27 Jan 2025 10:42:24 +0100
Source: libcamera
Architecture: source
Version: 0.4.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>
Changed-By: Dylan Aïssi <daissi@debian.org>
Closes: 1093688
Changes:
 libcamera (0.4.0-4) unstable; urgency=medium
 .
   * Add patch disabling libunwind integration (Closes: #1093688)
   * Add Forwarded field for fix_detection_libyuv.patch
Checksums-Sha1:
 a383dc7d8a9977e1e3a086670bc6f9ffe365940d 3404 libcamera_0.4.0-4.dsc
 230e4bb25d796d104311beca3498238f25ea146f 22712 libcamera_0.4.0-4.debian.tar.xz
 cfd8dc8e7f85c6ed35b9d9a98b2e0a9933c53236 24415 libcamera_0.4.0-4_amd64.buildinfo
Checksums-Sha256:
 80f7609d45933c03be149be4c6dad4cfaef428c70f27dd6677368f9eb89c0765 3404 libcamera_0.4.0-4.dsc
 3146d4f2a21a3ac003cd7941b2d1556c17b802f1c9b3ac7291f3aab83ebfd166 22712 libcamera_0.4.0-4.debian.tar.xz
 e8effa12d3d9cf6bbbf5f020a257e54275995d7ed431429f6bb4f57b82c69f9d 24415 libcamera_0.4.0-4_amd64.buildinfo
Files:
 2cb618b3f5a1f39b8204ac1e4a6c5b91 3404 libs optional libcamera_0.4.0-4.dsc
 b473c8046912540415d6b69b565e372d 22712 libs optional libcamera_0.4.0-4.debian.tar.xz
 6a1234ac6bc6f6979cff7ec5b40cf414 24415 libs optional libcamera_0.4.0-4_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEmjwHvQbeL0FugTpdYS7xYT4FD1QFAmeXYnMACgkQYS7xYT4F
D1QuZhAAsIZ9KnWFbJP9J5m+HAIyisKL+4PvlbB39gWBnfT3LuR3ojFVkhoYz4Vf
zUOC7TxdkGKHfC9XtoEQLhkHtIT2SePpwXRJ/gYz5oEdzEDGnztwZ7Ibx6qyn+SG
AroqnFC66XLwojKMkCyRsPooey4MYFtxjhkz1qJ4OM9Z68TVo2F6NJWn9TWFJXw3
QvDi3gO6lh/fmiCr1MH0OoaqAej1s1sUA4xP4to3q5VWCyIZJdj7BEkjCkuL9jez
Mzrn9pwkXOWKXd5HOVsbDF+ccN5nw3DAvk64sIsiWBdvV0XuW38Fb0S5QSiZfV1q
XVww2H4XMBQCAvKndbFBfgdo552Tdq/HKExx1ryLx3HwtDswrpzViPx/MP1NWYkb
rRF/koQjRN3BTxsbcvMErDgFIQaOysEWd0jKnIbtjVHrFVUoVT/ClsudgkFP1kH6
0+sHZ+Nqu2FhxGG90ulLbKh05YK5P5Ci6Y/pO0C6qXZkhgtntENjAcaV697MgBm5
oWwVWcyzQ9RA9MK5NAWpo1jSQXl/Y7aHhk9ghEmSY0SiSI9U/LSxQ5D3G06dsCBT
+qi2jwOxx7JZPXS7r3v2MAE47CHeWKAejKjit46AzLAYmjC9vxZnLhyWaf0LWRTp
L4E/hvr431SZnaCKtby7JSFVHXVClknwkD8cqK16Vusve48dPNY=
=bJMC
-----END PGP SIGNATURE-----

Attachment: pgpDMI_CX9yJN.pgp
Description: PGP signature


--- End Message ---
Reply to: