Bug 1249333 - dnf crash in select_next_target
dnf crash in select_next_target
Product: Fedora
Classification: Fedora
Component: dnf (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: packaging-team-maint
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-08-01 13:14 EDT by Zbigniew Jędrzejewski-Szmek
Modified: 2015-08-11 10:18 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-08-11 10:18:02 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
bt full (98.21 KB, text/plain)
2015-08-01 13:14 EDT, Zbigniew Jędrzejewski-Szmek
no flags Details

  None (edit)
Description Zbigniew Jędrzejewski-Szmek 2015-08-01 13:14:08 EDT
Created attachment 1058360 [details]
bt full

Description of problem:
Core was generated by `/usr/bin/python3 -OO /bin/dnf install qt5-qtbase-devel'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  select_next_target (err=<optimized out>, selected_full_url=<synthetic pointer>, 
    selected_target=<synthetic pointer>, dd=0x7ffcf8b71090)
    at /usr/src/debug/librepo/py3/librepo/downloader.c:667
667             if (target->state != LR_DS_WAITING)  // Pick only waiting targets

Version-Release number of selected component (if applicable):

How reproducible:
Comment 1 Zbigniew Jędrzejewski-Szmek 2015-08-01 14:39:57 EDT
> reproducible
dnf crashes ~60% of the time in this container, but in different places. So it seems to be some memory corruption issue.
Comment 2 Michal Luscon 2015-08-11 09:00:58 EDT

are you able to provide us a coredump with the exact versions of dnf, hawkey and librepo? Do you experience this only in containerized environment?
Comment 3 Zbigniew Jędrzejewski-Szmek 2015-08-11 10:18:02 EDT
I cannot reproduce this anymore. Unfortunately I have upgrade dnf to dnf-1.0.2-3.fc24.noarch in the mean time which might be related, but again might not.

Note You need to log in before you can comment on or make changes to this bug.