dnf5 builddep crashes in Fedora 41 container #1864
Comments
|
Reproducer:
At the point when almost everything is installed, dnf crashes. |
|
FreeIPA spec has '%autopatch -p1` but no patches in this scenario which causes a warning to be issued when parsing the spec file. However, unlike DNF4, DNF5 crashes when printing this warning. |
abbra
added a commit
to abbra/freeipa
that referenced
this issue
Nov 15, 2024
See rpm-software-management/dnf5#1864 Avoid warning in autopatch by using -q option to suppress warnings. Signed-off-by: Alexander Bokovoy <[email protected]>
|
Using |
abbra
added a commit
to abbra/freeipa
that referenced
this issue
Nov 15, 2024
See rpm-software-management/dnf5#1864 Avoid warning in autopatch by using -q option to suppress warnings. Signed-off-by: Alexander Bokovoy <[email protected]>
abbra
added a commit
to abbra/freeipa
that referenced
this issue
Nov 15, 2024
See rpm-software-management/dnf5#1864 Avoid warning in autopatch by using -q option to suppress warnings. Signed-off-by: Alexander Bokovoy <[email protected]>
abbra
added a commit
to abbra/freeipa
that referenced
this issue
Nov 15, 2024
See rpm-software-management/dnf5#1864 Avoid warning in autopatch by using -q option to suppress warnings. Signed-off-by: Alexander Bokovoy <[email protected]>
|
Hi there... Before opening a new issue here... could this be related? |
|
I think it might be a similar cause but there is no detail there. Two examples in the bug use |
m-blaha
added a commit
that referenced
this issue
Nov 18, 2024
This patch addresses undefined behavior that occurs when the RPM log callback function is invoked after the RpmLogGuard object has been destroyed. The issue arises because rpmlogCallbackData retains a reference to the destroyed object. The problem manifests during the execution of the builddep plugin command: 1. During Vars::detect_release, the RPM log callback is set via RpmLogGuard. 2. After the release version is detected, the RpmLogGuard object is destroyed. 3. A subsequent call to rpmSpecParse() by the builddep command may trigger the previously set log callback. 4. This results in undefined behavior because the callback data still points to the destroyed RpmLogGuard. By resetting the RPM log callback upon RpmLogGuard destruction, this patch ensures safe and predictable behavior. Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=2326535 Resolves: #1864
github-merge-queue bot
pushed a commit
that referenced
this issue
Nov 18, 2024
This patch addresses undefined behavior that occurs when the RPM log callback function is invoked after the RpmLogGuard object has been destroyed. The issue arises because rpmlogCallbackData retains a reference to the destroyed object. The problem manifests during the execution of the builddep plugin command: 1. During Vars::detect_release, the RPM log callback is set via RpmLogGuard. 2. After the release version is detected, the RpmLogGuard object is destroyed. 3. A subsequent call to rpmSpecParse() by the builddep command may trigger the previously set log callback. 4. This results in undefined behavior because the callback data still points to the destroyed RpmLogGuard. By resetting the RPM log callback upon RpmLogGuard destruction, this patch ensures safe and predictable behavior. Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=2326535 Resolves: #1864
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
DNF5 builddep crashes in Fedora 41 container. We use fedora-toolbox container in FreeIPA CI and part of the process we run is a rebuild of FreeIPA package. For that we need to install build dependencies with
dnf builddep. This works well for Fedora 40 and prior versions but since this morning we've got reliable crashes indnf builddep.It is reproducible outside of a cloud environment as well. Below is the stacktrace we get:
The text was updated successfully, but these errors were encountered: