From: Christian Heusel <gromit@archlinux.org>
To: Stephen Brennan <stephen@brennan.io>
Cc: linux-debuggers@vger.kernel.org,
Omar Sandoval <osandov@osandov.com>,
Petr Tesarik <petr@tesarici.cz>
Subject: Re: drgn 0.0.30 and libkdumpfile 0.5.5 incompatibility in Arch
Date: Thu, 2 Jan 2025 09:57:52 +0100 [thread overview]
Message-ID: <3eb3a0bd-232e-4015-8793-71b1662040ba@heusel.eu> (raw)
In-Reply-To: <8734i1lips.fsf@brennan.io>
[-- Attachment #1: Type: text/plain, Size: 2318 bytes --]
On 25/01/02 12:31AM, Stephen Brennan wrote:
> Stephen Brennan <stephen@brennan.io> 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-01-02 9:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 8:08 drgn 0.0.30 and libkdumpfile 0.5.5 incompatibility in Arch Stephen Brennan
2025-01-02 8:31 ` Stephen Brennan
2025-01-02 8:57 ` Christian Heusel [this message]
2025-01-02 13:57 ` Petr Tesařík
2025-01-02 14:13 ` Christian Heusel
2025-01-02 17:22 ` Stephen Brennan
2025-01-02 8:58 ` Petr Tesařík
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3eb3a0bd-232e-4015-8793-71b1662040ba@heusel.eu \
--to=gromit@archlinux.org \
--cc=linux-debuggers@vger.kernel.org \
--cc=osandov@osandov.com \
--cc=petr@tesarici.cz \
--cc=stephen@brennan.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox