FS#79260 - [kea] segfault

Attached to Project: Arch Linux
Opened by Vecíno (vecino) - Monday, 31 July 2023, 08:20 GMT
Last edited by Toolybird (Toolybird) - Monday, 31 July 2023, 20:15 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

We need to prepare a new Kea package with the current stable version 2.4.0 - https://www.isc.org/blogs/kea-2-4-0/ . The old version 2.2.0-7 causes segfault problems.


kea 2.2.0-7 - https://archlinux.org/packages/extra/x86_64/kea/
Everything is described here: https://gitlab.isc.org/isc-projects/kea/-/issues/2997
This task depends upon

Closed by  Toolybird (Toolybird)
Monday, 31 July 2023, 20:15 GMT
Reason for closing:  Upstream
Additional comments about closing:  See comments
Comment by Toolybird (Toolybird) - Monday, 31 July 2023, 08:36 GMT
> 2.2.0-7 causes segfault problems

Please post a backtrace with debug symbols [1]. Ensure gdb is installed, then it's usually as simple as:

$ coredumpctl gdb (then answer y when it asks "Enable debuginfod for this session?")
(gdb) set logging enabled
(gdb) bt (or bt full)

Then post gdb.txt

[1] https://wiki.archlinux.org/title/Debugging/Getting_traces
Comment by Vecíno (vecino) - Monday, 31 July 2023, 09:08 GMT
I'm so sorry, but I couldn't wait any longer - the dhcp server is on a production router and there were problems. Last night I deployed the 2.4.0 package I created. That solved the problem. So now I can no longer simulate the problem and provide you with logs from gdb.

I don't know what the correct procedure is to officially request a package update. Because kea 2.2.0-7 is already declared "Flagged out-of-date on 2023-07-26".
Comment by Christian Heusel (gromit) - Monday, 31 July 2023, 09:39 GMT
Does "coredumpctl list" list the trace as "missing"? Even when the bug didnt occur just now you can still get the trace for it like toolybird described it
Comment by Robin Candau (Antiz) - Monday, 31 July 2023, 10:03 GMT
For what it's worth, I do not experience such segfault issues on my side but I do agree that we should switch to the new `2.4.X` stable branch, which contains a bunch of bugfixes and new features [1].
I offered to the current maintainer to add myself as a co-maintainer for the package so I can update it and give some help maintaining the package for the future. I'm waiting for their input.

[1] https://gitlab.isc.org/isc-projects/kea/-/wikis/Release-Notes/release-notes-2.4.0
Comment by Toolybird (Toolybird) - Monday, 31 July 2023, 20:14 GMT
> no longer simulate the problem

As per comment from @gromit, coredumpctl is retrospective. You can still get a backtrace no problem. "man coredumpctl"

> I don't know what the correct procedure is to officially request a package update

The only procedure is "flag out of date" which is already done. This is documented in the BIG FAT blurb at the top of every ticket.

With no backtrace provided, this is basically a ticket for an outdated pkg (through sleight of hand), which is strictly banned as per aforementioned blurb.

Luckily, @Antiz is on the case and will hopefully get approval soon to co-maintain and upload a new pkg.

Loading...