Re: drgn 0.0.30 and libkdumpfile 0.5.5 incompatibility in Arch
Christian Heusel <[email protected]> Thu, 2 Jan 2025 09:57:52 +0100
| Newsgroups | org.kernel.vger.linux-debuggers |
|---|---|
| Message-ID | <[email protected]> |
On 25/01/02 12:31AM, Stephen Brennan wrote: > Stephen Brennan <[email protected]> writes: > > Hi Christian, Hey Stephen, > > > > I think you may already be aware of this, but I wanted to let you know > > that there's an incompatibility with drgn 0.0.30-2 and libkdumpfile > > 0.5.5-1 on Arch. libkdumpfile 0.5.5 changed some APIs in a > > backward-incompatible way. Building drgn against the new version fails, > > and running a version built against 0.5.4 of course fails due to the > > soname change. The current drgn 0.0.30-2 on Arch's repositories was > > built against 0.5.4. I was not yet aware of this! > > > > Thus a user installing drgn & libkdumpfile on Arch, who is fully > > up-to-date, gets this: > > > > ImportError: libkdumpfile.so.10: cannot open shared object file: No such file or directory > > > > The incompatibility is fixed in drgn's main branch by the changes in > > [1]. Unfortunately, that was merged after drgn 0.0.30 was released. > > Some major changes have been merged since then, so I don't think a > > 0.0.31 release is likely for a few months. So I think it may be a good > > idea to carry the two commits in [1] as downstream patches in a new > > 0.0.30-3 release. I'd be happy to implement those changes if it'd help. > > > > I'm Ccing the linux-debuggers mailing list for posterity, as well as > > Omar and Petr as an FYI. > > > > Thanks, > > Stephen > > > > [1]: https://github.com/osandov/drgn/pull/452 > > > Sorry, I was a bit mistaken here: > > 1. drgn 0.0.30 DOES build successfully with libkdumpfile 0.5.5. I > misread the changes there. As far as I can tell, there may be a small > memory leak when using 0.0.30 with 0.5.5, but nothing major. > > 2. I'd say the best way forward would be a simple rebuild of drgn > against libkdumpfile 0.5.5. > > Thanks, > Stephen thanks for your report and suggestions to fix the underlying issue! It turns out I somehow missed the soname bump in libkdumpfile's last release (also I'm a bit annoyed that it had one in a patch release) ... 😅 Sorry for any trouble this has caused you, this should be fixed with drgn 0.0.30-3! Additionally to the rebuild I included the patch you suggested at first, as it applied easily and fixes the lifetime issue! Cheers, Chris
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8AuW0VIoAT/8nJ0Dk7EdqkwZfj0FAmd2VQ8ACgkQk7EdqkwZ fj2EZRAAnnr8EpEAExzL5LwRJ9njdZKTSp1fZYTAdwXqZIvKPVQ4eOQLFnokYkLi tgancGZoIC4SbgqV2W4Yk8s+I0AuW+AmZc4qscKEddN6RW6FaRmaI9dhXamLt7pi AlS+iSjzVGMbodX6uIwZER7DCENwztAPhTjrnCbgmchEQ0dEc4PIk0SsqcvK157G O5Tf/hQNYtwXFGZlIBXjQLOxSYbuRC98SzrCTM0kfgygxy2N7VPD0LVWvn20NoQv 4dU+lse4MNWGvp5WZPGUr67R/m3suflVhJ68IC/ZrqorpwHT+FVo9Iq2BjJlcGmH 9Jbi/Swsj7bnFLYt4YYg9+a3H/ViuEyoAa9A+VzZ4qb6+NcoAqHnWhDrZqrH5Dr9 SXOsLukmPiCHSYF9q75jG7X0/zAjIodD92caGLPQWqzJxnM3z9LW0lomPPCWqZVh 6WLkWe/mr0HbAsX+9JUBKX5IXSBEzU1qYRd+oW8yu2Sxyf/PocJUNyMGUS0GTfZi U/m4UIx5IKO3fP2XQXxeMzB82R3WQ95Hprv/a1H44WKgsTO8+KLkJiYP97eXN217 O4CSZe/Y5AEUG/RMDttVdrO1TOhgX0gZn0vQiIyuZfu0Xgzi0B1IS7w2HkXPnQue b/b7dR3Wx64+IePY6Hu5Kdvt8ybyrl9cyGSjbRm3s0fRByRTY6A= =Dpfg -----END PGP SIGNATURE-----